Embed Size (px)
DESCRIPTION
Multi-tenancy refers to the ability to run multiple users of an application on a shared infrastructure. Such an infrastructure makes oblivious the need for having a dedicated infrastructure for each user or user group. This helps in the economies of scale by saving on the per user cost of operations. Several SaaS based applications like SalesForce.com provide a fine grained multi-tenant model. The common way to implement multi-tenancy is at the data layer, however this introduces a fair set of challenges when one decides to move to the cloud. Most solutions would focus around spreading the users across the cloud, however, what happens when a user is large enough to spread across the cloud? If you have an existing application, it requires a complete rewrite and also forces fairly significant changes to the existing data model. The current set of multi-tenant practices do not address the challenges of dynamic elasticity. The session tries to look at the challenges and possible solutions for the context.
Citation preview
1
Multi-tenancy in the Cloud
Vikas HazratiInphina Technologies
2
SaaS is a reality
3
multi-tenancy
4
multi-instance
5
it is not multi-instance
6
maturity
7
level of multitenancy
8
multi-tenant database
9
multi-tenancy in clouds
10
why it matters in the cloud
sell monthly or annual per seat subscriptionfraction as compared to onsite
reduce operating costmanage more with less
more money gives more room to innovate
11
should SaaS always be multitenant ?
12
prerequisite
is it a prerequisite for Cloud Computing?
13
how it is done today
14
coarse grained multi-tenancy
15
challenges
complexity
cost
16
challenges
elasticity challenge
17
it is so damn hard!
18
take a step back to the history
DOS
solution
19
lesson learnt
deal with the infrastructure
20
elastic middle-ware
service physicalresource
service abstraction
21
dealing with infrastructure
22
where are we?
23
elasticity is still an issue
24
google approach
sdk 1.3.6
17th aug 2010
namespaces api
25
application level namespace
26
user level namespace
27
maturity
28
concerns
security
impact of other clients
no I can pay, make me special
being forced into an upgrade
configurations / customizations to a level
user acceptance testing?
live date, whats that?
29
when not to go multi-tenant
not comfortable with security
high customization and tight integration
workload does not run in VM
30
references
31
http://www.inphina.comhttp://thoughts.inphina.com
contact us
