Database-Per-Tenant Architecture Using .Net Core and Azure SQL Database
summary
Architecture uses .Net Core with Azure SQL Database elastic pools and the Elastic Database tools to give each customer a database while sharing pool resources; shard map manager records mappings, local shard caches avoid thundering reads, and elastic jobs run cross‑tenant SQL. Pools host ~100–500 DBs, a DB spins up in ~30 seconds, and code automates creating new pools when full. Secrets live in separate Key Vaults and per‑database firewall rules grant temporary direct client access. Azure SQL elastic pools shard map manager elastic jobs
AI-written summary · about
chapters (11)
- 0:00Database-per-tenant intro
- 4:19Why choose DB-per-tenant
- 11:45Single vs multi-tenant
- 20:28Tenant isolation vs sharing
- 24:41Azure SQL Elastic Pools
- 28:52Infrastructure setup
- 34:09Elastic DB Tools
- 39:05Elastic DB Tools features
- 40:31Q&A: Merging tenants
- 42:17Q&A: Scaling to multi-tenant
- 44:43Q&A: DB provisioning
related talks
48mBuilding SaaS solutions on Azure SQL Database
58mKeeping the Noisy Neighbors Happy
14mBest Practices for Building Multi-Tenant Applications on Azure Cosmos DB
18mBuilding Performant Data Architecture for Multi-Tenant SaaS Apps
40mModern models of managing database fleets in Azure PaaS.
44mMulti-tenant SaaS apps made simple on Azure Cosmos DB for PostgreSQL
01h 15mChoose Azure SQL Database and Learn What Every Developer Should Know
27mMulti-tenant Saas apps made simple on Azure Cosmos DB for PostgreSQL