Multi-Tenancy Architecture Lessons Learned
Talkat Multi-TenancyCon North America 2023 · on Monday, 2023-11-06· at 13:30· W192ab, McCormick Place·
summary
Compares three architectures and makes a clear recommendation: avoid single website + multiple databases as it combines high code complexity with a hard-to-automate tenant lifecycle. Describes a real hardcoded tenant bug (tenant ID 045) and a noisy neighbor that consumed DB resources and caused timeouts. Shows retrofit costs — adding spaces to Octopus Deploy takes 9–11 months — and an internal octopus Cloud platform built to provision tenants in ~60 seconds. Notes deploy times: single DB ~30 minutes, isolated tenants ~5–10 minutes.
AI-written summary · about
chapters (6)
- 0:00Introduction to multi-tenancy
- 2:29Evaluating tenancy models
- 5:29Single website, single database
- 12:20Single website, multiple databases
- 17:33Isolated infrastructure
- 22:39Conclusion and recommendations
related talks
58mKeeping the Noisy Neighbors Happy
52mMultitenancy: cost-efficient and scalable patterns for Software-as-a-Service
28mDivide and Conquer: Multi-tenancy in Postgres
14mBest Practices for Building Multi-Tenant Applications on Azure Cosmos DB
25mMultitenancy with Rails
38mDeveloping Multi-Tenant Applications
25mMultitenant applications: how and why
29mHOW TO SAFELY SPLIT YOUR MULTI-TENANT APPLICATION (BASED ON REAL EXAMPLES!)