Azure Cosmos DB Performance Tuning
summary
Terraform scripts provision Cosmos DB (repo: amreshkris/cosmosdb-conf-tf-mongo) with Mongo API, set auto-scale 400→4,000 at DB or collection level, and use serverless for dev. Monitoring highlights RU spikes to 100% causing 429s, so enable server-side retry and metrics-driven fixes. Performance changes: sharded by foodCategory, added indexes and TTL, introduced a synthetic product key (category+subcategory), upgraded server from 3.6→4.2, and briefly bumped RU to 20,000 for bulk load — improvements reduce throttling and stabilize latency.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:56Cosmos DB
- 14:11Insights Monitoring
- 17:44Metrics Monitoring Shard Usage
- 19:59Server Side Retry
- 21:08Scalability for Read & Write
- 24:42Scalability on DB or on Collection - Comparison
related talks
48mPerformance tuning for Azure Cosmos DB
01h 00mCost cutting strategies for Azure Cosmos DB
01h 00mAzure Cosmos DB : A brief Note for Developers
01h 02mAzure Cosmos DB - Low Latency and High Availability at Planet Scale
18mIntelligent Resource Optimization: Mastering Azure Cosmos DB for Enterprise Workloads
08mOptimize for the Best Cost and Performance for Azure Cosmos DB NoSQL API
14mHow to achieve good cost/performance with Azure Cosmos DB elasticity
54mSay Yes to NoSQL for the .NET SQL Developer