Building Performant Data Architecture for Multi-Tenant SaaS Apps
summary
Shows Azure Cosmos DB for PostgreSQL’s built‑in sharding: a function taking table, sharding key, shard count (default 32) and co-locate with, used to shard tenant, product and orders tables on tenant_id so related rows live on the same worker node. Demonstrates that adding a tenant_id filter drops tasks from three to one for updates and joins, that scale‑out adds a node and performs tenant isolation by creating and moving a shard live, and that auto sharding plus monitoring views reveal per‑tenant query patterns.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:27What is MultiTenant
- 1:42Cosmos DB for PostgreSQL
- 3:24Simple Store
- 4:36Demo
- 11:30Tenant Isolation
- 12:40Demo Tool
- 15:32Demo 3 Available Views
- 16:14Summary
related talks
27mMulti-tenant Saas apps made simple on Azure Cosmos DB for PostgreSQL
44mMulti-tenant SaaS apps made simple on Azure Cosmos DB for PostgreSQL
52mBuilding Distributed OLTP with Azure Cosmos DB for PostgreSQL
14mBest Practices for Building Multi-Tenant Applications on Azure Cosmos DB
28mDivide and Conquer: Multi-tenancy in Postgres
58mKeeping the Noisy Neighbors Happy
46mDesign and build multi-tenant SaaS apps at scale with Azure Cosmos DB
25mSaaS on Rails on PostgreSQL