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.

1. Multi-tenancy in the Cloud
Vikas Hazrati
Inphina Technologies
1

2. SaaS is a reality
2

3. multi-tenancy
3

4. multi-instance
4

5. it is not multi-instance
5

6. maturity
6

7. level of multitenancy
7

8. multi-tenant database
8

9. multi-tenancy in clouds
9

10. why it matters in the cloud
sell monthly or annual per seat subscription
fraction as compared to onsite
reduce operating cost
manage more with less
more money gives more room to innovate
10

11. should SaaS always be
multitenant ?
11

12. prerequisite
is it a prerequisite for Cloud
Computing?
12

13. how it is done today
13

14. coarse grained multi-tenancy
14

15. challenges
complexity
cost
15

16. challenges
elasticity challenge
16

17. it is so damn hard!
17

18. solution
take a step back to the history
DOS
18

19. lesson learnt
deal with the infrastructure
19

20. elastic middle-ware
service physical
resource
service abstraction
20

21. dealing with infrastructure
21

22. where are we?
22

23. elasticity is still an issue
23

24. google approach
sdk 1.3.6
th
17 aug 2010
namespaces api
24

25. application level namespace
25

26. user level namespace
26

27. maturity
27

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?
28

29. when not to go multi-tenant
not comfortable with security
high customization and tight integration
workload does not run in VM
29

30. references
30

31. contact us
vhazrati@inphina.com
http://www.inphina.com
http://thoughts.inphina.com
31