FREE STUDY NOTES · AZ-305

Azure Cosmos DB consistency levels explained

The five Cosmos DB consistency levels, what each guarantees, and the latency and availability trade-offs.

From Ultra Transcenders AZ-305 by Tony Rough (publishing soon)

Consistency is a trade-off between how fresh a read is and how fast and available writes are. Cosmos DB offers five levels, and the choice affects which service level agreements apply.

Figure 7.1 lays the five levels out on a single spectrum and shows where the SLA and multi-write-region limits fall.

The five Cosmos DB consistency levels on a spectrum from Strong (freshest reads) to Eventual (fastest, most available writes). Strong has no multi-region write-latency SLA and is not available on accounts with multiple write regions; bounded staleness is the strongest level that carries that SLA.
Figure 7.1: Cosmos DB consistency levels, strongest to weakest
Consistency (strongest first) Write-latency SLA on multi-region accounts?
Strong No (a write must commit in every region)
Bounded staleness Yes (the strongest level with this SLA)
Session, Consistent prefix, Eventual Yes

Get the whole book

This note is one section of Ultra Transcenders AZ-305: Designing Microsoft Azure Infrastructure Solutions, an independent study guide that explains every topic the exam covers by technology, with comparison tables, diagrams and the common traps, plus a glossary linked to Microsoft Learn.

Amazon.co.ukKindle: coming soonPaperback: coming soon
Amazon.comKindle: coming soonPaperback: coming soon

Publishing soon on Amazon in Kindle and paperback editions.

About the book · Free AZ-305 glossary · All AZ-305 study notes

More AZ-305 study notes