Azure Cosmos DB Serverless Unleashed
summary
Explains when serverless cuts costs and when provisioned throughput stays necessary, with concrete limits: consumption-based billing charges RUs used and storage, serverless caps at 5,000 RUs/sec and 50 GB per container, supports single-region with zone redundancy, and disallows shared throughput or programmatic throughput changes. Shows Table API demo comparing insert/replace/delete latency and a cost example where 20M RUs/month favors serverless while 250M RUs/month can make it pricier.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:46Overview
- 2:10Reserved throughput
- 3:23Cosmos DB is serverless
- 6:10Provision
- 7:13limitations
- 7:55zone availability
- 10:37change throughput
- 12:45critical workloads
- 13:51use cases
- 15:46solutions
- 16:05demos
- 21:59questions
related talks
22mAzure Cosmos DB Serverless Unleashed
15mReducing database costs to $1 with data modeling, Azure Web PubSub, and the Cosmos serverless plan
49mSQL Server vs Azure Cosmos DB
01h 00mAzure Cosmos DB : A brief Note for Developers
01h 00mCost cutting strategies for Azure Cosmos DB
14mHow to achieve good cost/performance with Azure Cosmos DB elasticity
01h 13mBuilding Planet Scale .NET Apps with Azure Cosmos DB
01h 02mAzure Cosmos DB - Low Latency and High Availability at Planet Scale