Cloud-Native Apps using Azure Cosmos DB, ready for recovery!
summary
Shows how Azure Cosmos DB with multi-region writes and Geo-Replication recovers an app: a two-region setup fails over automatically and continues serving writes with under two seconds replication in the demo. Uses Azure Functions (note: each function needs its own lease collection) and simulates outages with Azure Kael's Studio. Presents concrete SLA math: single-region compound SLA ≈99.940% (~25 minutes/month), two-region nearly 99.99% (under five minutes/month), and the failover works without code changes.
AI-written summary · about
chapters (10)
- 0:00Intro
- 2:02Cosmos DB Global Distribution
- 4:19Global Replication and Automatic Failover
- 5:54Cosmos DB Consistency Levels
- 7:01Cosmos DB - Session Consistency
- 7:42Cosmos DB - Eventual Consistency
- 9:25What to expect during outages and why the consistency level and SLA matters?
- 11:06Building an Architecture - Cosmos Single-region
- 13:49How to test failover? - Chaos Studio
- 16:51Sample Scenario 2 - Multi-region Writes
related talks
45mGetting the Most from NoSQL in the Cloud with Azure Cosmos DB
01h 02mAzure Cosmos DB - Low Latency and High Availability at Planet Scale
51mAchieving Resiliency With A Multi-Cloud Or Multi-Region Approach
01h 01mAzure SQL Database-Business Continuity During Disaster
09mMulti-Region Replication & DR for Distributed Postgres in Azure Cosmos DB
47mPerfecting business continuity for Azure SQL DB
43mDatabase capabilities you need for your next awesome app Q&A
01h 03mAzure Cosmos DB - The Best NoSQL Database You're Probably Not Using (Yet)