Azure Cosmos DB - Low Latency and High Availability at Planet Scale - Kevin Pilch

This talk was recorded at NDC London in London, England. #ndclondon #ndcconferences #developer #softwaredeveloper
Attend the next NDC conference near you:
ndcconferences...
ndclondon.com/
Subscribe to our CZcams channel and learn every day:
/ ‪@NDC‬
Follow our Social Media!
/ ndcconferences
/ ndc_conferences
/ ndc_conferences
#azure #api #sql #database #architecture #cloud
Azure Cosmos DB is a fully-managed, multi-tenant, distributed, shared-nothing, horizontally scalable database that provides planet-scale capabilities and multi-model APIs for Apache Cassandra, MongoDB, Gremlin, Tables, and the Core (SQL) APIs. It currently powers many mission-critical services both within Microsoft (such as Microsoft Teams and Active Directory) and across large-scale Fortune 500 organizations (such as Walmart and Adobe).
This talk covers the internal architecture of Azure Cosmos DB and how it achieves high availability, low latency, and scalability. I will first cover the design of the storage engine, with particular emphasis on ensuring high availability and scalability through partitioning and replication. Next, I will zoom in on the request routing gateway to see how it has evolved to solve the well-known multi-tenant cloud infrastructure challenges of containing noisy neighbors and limiting blast radius. Lastly, I will discuss performance as a feature and as a culture. I will cover what I measure and how we think about SLOs to achieve and maintain low latency.
Building planet-scale services necessitates solving complex scalability challenges and making numerous tradeoffs across various components in the product. I look forward to sharing my experiences and lessons learned in building Azure Cosmos DB.

[@weifengmao]

How about system text json support in the dotnet client? Its 2024 now

[@flygonfiasco9751]

This would be great imo but I think the cosmos sdk team doesn’t want to release a breaking change to add support for stj. But yeah, you’re right, it’s time

[@ernest1520]

Cosmos DB is a huge paradox. A cloud-native database that "just works" but requires you to control throughput in fine, per-container details if you want to avoid throttling caused by using shared throughput (and in most enterprise systems you do). Alternatively you can switch to a Serverless plan which is a pay-per-use model, but guess what- no multi-region support. A "serverless" database that's tied to a single region...