Turning Growing Pains To Growing Wins With Azure Cosmos DB
summary
Portnox triples load tripled scale in one year and eliminates frequent 429 throttles by enabling autoscale and by pre-scaling based on metrics like Service Bus queue length and authentications/sec. Noisy tenants that hit 100% RU move to their own container or database, and a real failure mode forces refactor when a partition hits the 20 gigabyte partition limit. Read-heavy collections get Azure Redis caching, large or time-series blobs move to Azure Blob storage, and continuous cleanup smooths spikes.
AI-written summary · about
chapters (4)
related talks
01h 13mBuilding Planet Scale .NET Apps with Azure Cosmos DB
18mIntelligent Resource Optimization: Mastering Azure Cosmos DB for Enterprise Workloads
33mDriver for Data-Driven Change - Azure Cosmos DB Performance, Security & Cost Optimization Done Right
32mAzure Cosmos DB Performance Tuning - Sonal Pathak & Amresh Krishanmurthy
01h 02mAzure Cosmos DB - Low Latency and High Availability at Planet Scale
46mDesign and build multi-tenant SaaS apps at scale with Azure Cosmos DB
01h 00mCost cutting strategies for Azure Cosmos DB
20mManage Scaling, While Keeping Costs Under Control. Challenge Accepted.