The Role of Multi-Tenancy in a Cloud Environment
Software vendors and enterprises wondering whether or not to multi-tenant-enable public, private, and hybrid clouds applications, and how to do so, find it challenging to get clear answers. The debate surrounding these questions has so far tended to crystallize around extreme positions, but a more pragmatic approach is emerging.
Summary
Impact
Ovum view
Key messages
Cloud computing has a complex relationship with multi-tenancy
A multi-faceted relationship
It depends on the type of cloud and the type of multi-tenancy
Clouds support both application and architecture-level multi-tenancy
The debate about the nature of multi-tenancy
Principled people battle pragmatists
Multi-tenancy impacts both vendors and products
Business users are increasingly aware of multi-tenancy
SaaS is the application-level multi-tenancy champion
SaaS is a public cloud component
Application-level multi-tenancy is the cornerstone of SaaS
Most software vendors have now turned to SaaS
SaaS is dragged toward architecture-level multi-tenancy
IaaS and private clouds bring back architecture-level multi-tenancy
ASPs bring architecture-level multi-tenancy into disrepute
Virtualization and IaaS pulls it back from the brink
IaaS offers a platform and channel to market
Private clouds follow the IaaS route
PaaS is the potential disruptor
Important but ignored
PaaS helps but constrains
PaaS has two approaches to application-level multi-tenancy
There are many ways to skin the multi-tenancy cat
Application-level multi-tenancy
From shared on-premise services to multi-tenant online SaaS applications
Application-level multi-tenancy impacts all application layers
Application-level multi-tenancy impacts application management
There are various approaches to application-level multi-tenancy
Architecture level multi-tenancy
Physical architecture sharing
Virtual resource sharing
Better management, no redesign
OSS/BSS mediation layer
The two approaches are likely to be increasingly mixed
First-generation SaaS vendors had to build their own infrastructure
Second-generation SaaS vendors turn to public clouds
Elasticity is a challenge at both levels
Multi-tenancy becomes a business-centric continuum
Application-level multi-tenancy is maturing
The market is increasingly aware of its merits
The market is increasingly aware of its challenges
Success brings diversity
The SaaS debate is moving beyond application-level multi-tenancy
Architecture-level multi-tenancy is standing its ground for now
Architecture-level multi-tenancy is rising
Application-level multi-tenancy remains the way forward
Business decisions are based on a variety of criteria
Recommendations
Recommendation to users
Get interested in multi-tenancy
Adopt a rational approach to multi-tenancy
Recommendations to vendors
Be articulate about the details and impact of multi-tenancy design choices
Choose application-level multi-tenancy as the end goal
The picks and shovels providers will be the winner of the multi-tenancy gold rush
Impact
Ovum view
Key messages
Cloud computing has a complex relationship with multi-tenancy
A multi-faceted relationship
It depends on the type of cloud and the type of multi-tenancy
Clouds support both application and architecture-level multi-tenancy
The debate about the nature of multi-tenancy
Principled people battle pragmatists
Multi-tenancy impacts both vendors and products
Business users are increasingly aware of multi-tenancy
SaaS is the application-level multi-tenancy champion
SaaS is a public cloud component
Application-level multi-tenancy is the cornerstone of SaaS
Most software vendors have now turned to SaaS
SaaS is dragged toward architecture-level multi-tenancy
IaaS and private clouds bring back architecture-level multi-tenancy
ASPs bring architecture-level multi-tenancy into disrepute
Virtualization and IaaS pulls it back from the brink
IaaS offers a platform and channel to market
Private clouds follow the IaaS route
PaaS is the potential disruptor
Important but ignored
PaaS helps but constrains
PaaS has two approaches to application-level multi-tenancy
There are many ways to skin the multi-tenancy cat
Application-level multi-tenancy
From shared on-premise services to multi-tenant online SaaS applications
Application-level multi-tenancy impacts all application layers
Application-level multi-tenancy impacts application management
There are various approaches to application-level multi-tenancy
Architecture level multi-tenancy
Physical architecture sharing
Virtual resource sharing
Better management, no redesign
OSS/BSS mediation layer
The two approaches are likely to be increasingly mixed
First-generation SaaS vendors had to build their own infrastructure
Second-generation SaaS vendors turn to public clouds
Elasticity is a challenge at both levels
Multi-tenancy becomes a business-centric continuum
Application-level multi-tenancy is maturing
The market is increasingly aware of its merits
The market is increasingly aware of its challenges
Success brings diversity
The SaaS debate is moving beyond application-level multi-tenancy
Architecture-level multi-tenancy is standing its ground for now
Architecture-level multi-tenancy is rising
Application-level multi-tenancy remains the way forward
Business decisions are based on a variety of criteria
Recommendations
Recommendation to users
Get interested in multi-tenancy
Adopt a rational approach to multi-tenancy
Recommendations to vendors
Be articulate about the details and impact of multi-tenancy design choices
Choose application-level multi-tenancy as the end goal
The picks and shovels providers will be the winner of the multi-tenancy gold rush
