NoSQL, YesCosmos: Build that Eventually Consistent Application using Azure Cosmos DB
summary
Azure Cosmos DB provides five tunable consistency levels and the demo builds an e‑commerce flow where an order is written, an Azure Function persists it to Cosmos DB, and a consumer creates invoices from the change feed — reducing order latency while accepting temporary divergence of 5–15 seconds. Practical tips include using session tokens to read your own writes, using upsert for idempotent retries, and configuring last-writer-wins or custom conflict resolution via a merge stored procedure; lowering client consistency speeds bulk ingestion but cannot be raised per request.
AI-written summary · about
chapters (12)
- 0:00Eventually consistent apps
- 1:07Orchestrated request patterns
- 2:53Event-driven with Cosmos DB
- 4:20Cosmos DB consistency models
- 8:14Consistency levels per request
- 10:23Handling inconsistent reads
- 11:46Multi-region writes conflict
- 13:31Idempotent operations
- 14:14Asynchronous programming
- 14:58Change feed for reactive models
- 15:18Async pub-sub with Cosmos DB
- 17:02Summary
related talks
45mGetting the Most from NoSQL in the Cloud with Azure Cosmos DB
01h 02mFrom SQL to Azure Cosmos DB
01h 01mFrom SQL to Azure Cosmos DB
01h 01mServerless & Schemaless with Azure Functions and CosmosDB
01h 02mAzure Cosmos DB - Low Latency and High Availability at Planet Scale
54mSay Yes to NoSQL for the .NET SQL Developer
39mBuilding Event-Driven Systems at Scale with Cosmos DB
43mDatabase capabilities you need for your next awesome app Q&A