Azure SpendOps – The Art of Effectively Managing Azure Costs
summary
Shows how to implement SpendOps by intercepting Cosmos DB responses to record the request charge per operation, aggregating charges by feature in CI/CD tests and production, and using release gates to block changes that raise cost. Demonstrates practical tactics: co‑location of entities to one container, choosing high‑cardinality partition keys, using the emulator for test metrics, and provision throughput at database level. Highlights surprising math: ~50 million RUs = $0.01 and 400 RU minimum ≈ $37/month.
AI-written summary · about
chapters (11)
- 0:00Intro
- 2:10What is Cosmos DB?
- 3:56My Cosmos Journey
- 6:50ORM Frameworks
- 9:04What is a Request Unit (RU)?
- 13:45Writing the query
- 15:33Query Optimization
- 20:36Optimize Partitions
- 23:41Request Charge
- 24:00Automation - Implementation Details
- 29:36Production ideas
related talks
18mIntelligent Resource Optimization: Mastering Azure Cosmos DB for Enterprise Workloads
53mAzure Cost Management
40mA cheapskate's guide to Azure
36mFinOps & Observability: technical implementation
23mFinOps and Cloud Cost Optimization
46mCloud cost chaos? Get clarity with FinOps cloud cost management
19mDoing FinOps Right: Stories of (Anti)Patterns and Spendthrift Architectures
37mA startup's infrastructure - how to make scaling a sales, not a tech issue