Cost cutting strategies for Azure Cosmos DB
summary
Explains concrete levers to cut Cosmos DB bills: physical partitions split at 50 GB or 10,000 RU and autoscale vs manual thresholds (watch the 6,000 RU trigger); pick a high‑cardinality partition key or create a read‑optimized container and sync with change feed; use indexing: NONE for bulk loads, exclude large text properties, add composite indexes for multi‑filter/order‑by; tune pagination (default maxItemCount 100) and prefer point reads (id+partition key ≈ 1 RU); consider dedicated gateway cache for hot reads and use SDK indexing metrics to test index suggestions.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:33Database partitioning fundamentals
- 5:11Physical and logical partitions
- 14:08Partition key strategy
- 21:28Query pagination
- 23:40Indexing policies
- 33:32Advanced indexing techniques
- 37:52Performance optimization tools
- 40:48Using indexing metrics
- 43:30Integrated cache and order by
- 47:00Demonstrations and conclusion
related talks
48mPerformance tuning for Azure Cosmos DB
08mOptimize for the Best Cost and Performance for Azure Cosmos DB NoSQL API
52mPerformance tuning for Azure Cosmos DB
14mHow to achieve good cost/performance with Azure Cosmos DB elasticity
33mDriver for Data-Driven Change - Azure Cosmos DB Performance, Security & Cost Optimization Done Right
18mIntelligent Resource Optimization: Mastering Azure Cosmos DB for Enterprise Workloads
49mSQL Server vs Azure Cosmos DB
01h 03mData Modeling and Partitioning in Azure Cosmos DB