SaaS Deep Dive: Designing & Building Multi-Tenant Solutions
summary
Covers a concrete SaaS stack: tenant registration service, user management tied to OpenID Connect, tokens that carry user and tenant context through microservices, and a data access layer that applies per-request routing to either silo vs pooled storage (per-tenant database or shared DB keyed by tenant). Shows runtime-scoped isolation using an isolation token manager that fetches tenant-scoped credentials from a tenant access manager, and stresses tenant-aware logging and metrics for troubleshooting and billing.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:40The SaaS architecture landscape
- 5:18Provisioning a new tenant
- 7:56Tenant context everywhere
- 9:32Building multi-tenant microservices
- 12:49Partitioning data
- 14:30A microservices-by-microservices decision
- 15:23Isolating tenant resources
- 16:52The challenge of pool-based isolation
- 17:35Runtime scoped access with policies
- 19:14Takeaways
related talks
28mSimplify multi-tenant microservice applications
58mKeeping the Noisy Neighbors Happy
27mSingle Mesh vs Multi Mesh- Tradeoffs for Enterprise Multi-Tenant Support- Ding Shaojun (Iris Ding) & Zhang Huailong (Steve Zhang), Intel
28mSaaS migration and modernisation
37mRunning SaaS multi-tenant applications on ASP.NET Core, Azure
50mMultitenancy from scratch
42mIntegration and Conversation Patterns in SaaS Applications
42mIntegration and Conversation Patterns in SaaS Applications