Building a multi-tenant application using 45.000 databases - Henry Been - Codemotion Rome 2018
Download as PPTX, PDF1 like161 views
The document discusses building a multi-tenant application using 50,000 databases, highlighting the advantages of using a database per tenant such as unlimited scalability and tenant isolation. It outlines the issues with a single database model, including cost and failure risks, while also providing insights into tools and processes needed to implement such a solution. The presentation includes considerations for legacy applications, cost-efficiency strategies, and the challenges of migration.
![Why only a single database?
•Single point of failure
•More expensive
•Cannot grow in small steps
•Scaling up is failing up [1]
[1] Scalability rules: 50 principles for Scaling Web Sites](https://image.slidesharecdn.com/been-50-180709091359/85/Building-a-multi-tenant-application-using-45-000-databases-Henry-Been-Codemotion-Rome-2018-5-320.jpg)
Building a multi-tenant application using 45.000 databases - Henry Been - Codemotion Rome 2018
- 1. Buidling a multi-tenant application using 50k databases Henry Been ROME - APRIL 13/14 2018
- 3. Server 1 Server 2 Server 3 Server 4 Server n Database loadbalancing
- 5. Why only a single database? •Single point of failure •More expensive •Cannot grow in small steps •Scaling up is failing up [1] [1] Scalability rules: 50 principles for Scaling Web Sites
- 6. Server 1 Server 2 Server 3 Server 4 Server n DB loadbalancing DB DB DB DB DB
- 7. Using a database per tenant •Unlimited scaleability •Isolation of failure •Roughly 2,5 times cheaper •100% tenant isolation •Better fit for legacy applications
- 8. 100% tenant isolation •Snapshot backup/restore •Recover to point in time •Compliance •Limited authorization risks
- 9. Better fit for legacy applications •Designed for single tenant, single db •Allows for move to the cloud •Use case I will present
- 10. Disclaimer!
- 11. "The Long Road Ahead" (CC BY-NC-ND 2.0) by CC Chapman
- 12. SnelStart How it happened at "Incidental Expenses" (CC BY-NC 2.0) by tim ellis
- 26. So…. what do I need? "tools" (CC BY-NC-ND 2.0) by ᴾᴴᴵᴸ
- 27. Services platform •Login •Retrieve connection string •Create tenant •Destroy tenant •Backup tenant •Restore tenant
- 28. Catalog •Customers / Accounts •Users •Tenants •Authorizations •Operations • Create / destroy • Backup/restore • Etc
- 29. User Directory
- 30. A pointer on operations •Modeled as a state machine, with steps •Designed for failure and resume •Properties •Retry •Idempotentcy •Reentrant •Queue vs. database
- 32. User Directory
- 33. Demo time! "Mad Science!" (CC BY-NC 2.0) by FallenPegasus
- 35. •Unlimited scaleability •Isolation of failure •Migration of legacy •More effort to build! Wich way forward?
- 36. "Balanced Stones.Sausalito" (CC BY-SA 2.0) by DrPleishner
- 37. HENRY BEEN Independent geek E: consultancy@henrybeen.nl T: @henry_been L: linkedin.com/in/henrybeen W: henrybeen.nl Do try this at home!
Editor's Notes
- #11: Image from Wikipedia, https://upload.wikimedia.org/wikipedia/commons/c/ca/DART_UML_DART_2011_2013_RAW.svg Dislaimer: What I will be sharing, applies best to traditional upscaling relational databases Less to infinity scaling databaes like DynamoDB or CosmosDB
- #12: Image from: "The Long Road Ahead" (CC BY-NC-ND 2.0) by CC Chapman The rest of this 40 minutes: Introduction of one of the largest use cases in the world Introduction of two variations of this partern How to go about designing such a solution
- #14: "Incidental Expenses" (CC BY-NC 2.0) by tim ellis
- #17: The Masterplan
- #18: The Masterplan
- #20: By now you might want to say, whut? That database is used by only 1 or 2 users? Isn’t that idle half the time? Nope! Actually it is idle 99% of the time. So, how can that be cost effective?
- #22: This and next five images from MSDN, Microsoft – with permission
- #28: "tools" (CC BY-NC-ND 2.0) by ᴾᴴᴵᴸ
- #31: Actually the architecture is more complex than first shown - Showing more services used on the back-end
- #38: Actually the architecture is more complex than first shown - Showing more services used on the back-end
- #39: Addeda gain: for comparision
- #40: "Mad Science!" (CC BY-NC 2.0) by FallenPegasus
- #41: "Keep Moving Forward" (CC BY 2.0) by IrfaanPhotography
- #43: "Balanced Stones.Sausalito" (CC BY-SA 2.0) by DrPleishner