CosmosDB: Usage in a Real Project
summary
A mobile app and website project needed persistent storage for customers' order history after Redis proved unsuitable. The talk explains why Redis didn't fit, how the team selected and integrated Azure Cosmos DB, specific features and pitfalls of Cosmos DB, and how they optimized queries and infrastructure costs.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 2:21Company and projects
- 5:10Monolith and Redis issues
- 8:04Choosing Cosmos DB
- 9:50Cosmos DB setup
- 13:51Sharding and partitions
- 21:08Data modeling in Cosmos
- 24:18Mongo API usage
- 26:47SQL API usage
- 28:55Switching from Redis to Cosmos
- 32:45Change Feed and event processing
- 36:40Testing and integration
- 41:25Cosmos features and issues
- 46:26Consistency levels
- 48:11Query optimization
- 51:01Monitoring and metrics
- 53:06Summary
- 54:31Q&A
related talks
19mA journey through Cosmos to understand users
43mDatabase capabilities you need for your next awesome app Q&A
18mNoSQL, YesCosmos: Build that Eventually Consistent Application using Azure Cosmos DB
03h 30mAmericas Live Stream
50mAzure Cosmos DB - Technical Deep Dive
27mIntegrating Azure Cosmos DB with the Azure Ecosystem
01h 01mFrom SQL to Azure Cosmos DB
57mCosmosDB 101: Basics and quickstart
