Multi-Tenancy Requires More Than Just Isolating Customers

@Alan

 

 

PaaS is the weird in between case, agreed. It's both IaaS and SaaS in one big network box. I think some services offered - messaging, workflow, etc... - fall into the same category as infrastructure/network services while others - data, specifically - end up falling into the SaaS-style category.

 

 

Thus PaaS has to somehow marry both. Not an easy task and I unfortunately don't have a technical architecture ready to deal with that one, but it will likely need to (for production/publishing anyway) treat the entire stack more like IaaS than SaaS to handle the distinction. Or perhaps it'll end up a combination, with an "application" being coupled to a customer for purposes of billing/application of policies.

 

 

Lori