Getting the Most from NoSQL in the Cloud with Azure Cosmos DB
summary
Concrete claims and demos: Cosmos DB shows 5–6 ms median reads and sub‑10 ms writes, a 4 9s SLA and push‑button geo‑replication to 40+ regions. Live code uses the .NET SDK to write five JSON movies, query with LINQ and SQL‑style queries, and connect via MongoDB protocol; a StackOverflow subset loads into Gremlin graph and the change feed plus Azure Functions bindings run. Costs use provisioned request units and an on‑disk encryption + local emulator; partitioning and throughput sizing remain the hard parts.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 2:47What is Cosmos DB
- 11:10Schemas
- 12:06SDKs
- 14:57Request Units
- 18:11Create a New Collection
- 25:51Stored Procedures
- 27:02Encryption
- 27:50Change Feed
- 29:06Local Development Emulator
- 30:09Azure Functions
- 31:12Document Based API
- 32:35Gremlin API
- 33:04Stack Overflow
- 35:20MongoDB
- 38:49Slides
- 39:00Multiple Consistency Models
- 39:54Replication
- 40:08Replication Demo
- 40:39Use Cases
- 42:12Anticipating throughput needs
- 43:41Whats coming next
- 44:58Outro
related talks
01h 03mAzure Cosmos DB - The Best NoSQL Database You're Probably Not Using (Yet)
54mSay Yes to NoSQL for the .NET SQL Developer
03h 30mAmericas Live Stream
16mAzure Cosmos DB: A look at the Universe
55mSQL Server vs Azure Cosmos DB
01h 02mAzure Cosmos DB - Low Latency and High Availability at Planet Scale
49mSQL Server vs Azure Cosmos DB
33mDriver for Data-Driven Change - Azure Cosmos DB Performance, Security & Cost Optimization Done Right