Building Planet Scale .NET Apps with Azure Cosmos DB
summary
Azure Cosmos DB scales by splitting partitions (50 GB or 10,000 RUs each) and shines for global low latency with claims like 1 RU per 1KB read and a 10 ms SLA / 5 nines availability when multi‑region is configured. The .NET SDK requires a singleton CosmosClient, supports direct (TCP) vs gateway modes, autoscale and a new Dynamic scaling per-partition feature, and integrates with OpenTelemetry + Application Insights to capture request charges (creates ≈7 RUs), point reads, cross‑partition query round trips and rich diagnostics.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:44Performance
- 1:40Azure Cosmos DB
- 3:47How Cosmos DB scales
- 5:22Partitioning
- 6:22Data Distribution
- 9:38Throughput Distribution
- 10:50Partition Key Characteristics
- 12:09Partition Key Strategies
- 14:11Global Distribution
- 17:09Consistency
- 21:31Conflicts
- 23:02Azure Portal
- 27:11Cosmos DB Options
- 32:42Resource Model
- 33:58Gateway Mode
- 35:30Sample App
- 46:06Monitoring
- 48:27Open Telemetry
- 53:41Application Insights
related talks
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
16mAzure Cosmos DB: A look at the Universe
49mSQL Server vs Azure Cosmos DB
45mGetting the Most from NoSQL in the Cloud with Azure Cosmos DB
59mPlanet scale or planet fail?
01h 00mCost cutting strategies for Azure Cosmos DB
14mHow to achieve good cost/performance with Azure Cosmos DB elasticity