# Consistency Models in Azure Cosmos DB: From Strong to Eventual

DevFeed: [Consistency Models in Azure Cosmos DB: From Strong to Eventual](<https://devfeed.tech/articles/consistency-models-in-azure-cosmos-db-from-strong-to-eventual-39561.md>)

Original publisher: [Read original article](<https://ankit-rana.com/logs/09-cosmosdb-consistency-models/>)

Author: hello@ankit-rana.com

Published: 2026-03-16T00:00:00Z

Content type: article

Language: en

Sources: [Ankit Rana | Mechanical Sympathy](<https://devfeed.tech/sources/ankit-rana-mechanical-sympathy.md>)

Topics: [consistency](<https://devfeed.tech/topics/consistency.md>), [Databases](<https://devfeed.tech/topics/databases.md>), [Availability](<https://devfeed.tech/topics/availability.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [Replication](<https://devfeed.tech/topics/replication.md>), [Azure](<https://devfeed.tech/topics/azure.md>)

Tags: [availability](<https://devfeed.tech/tags/availability.md>), [cloud-architecture](<https://devfeed.tech/tags/cloud-architecture.md>), [consistency](<https://devfeed.tech/tags/consistency.md>), [cosmosdb](<https://devfeed.tech/tags/cosmosdb.md>), [database-design](<https://devfeed.tech/tags/database-design.md>), [databases](<https://devfeed.tech/tags/databases.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [latency](<https://devfeed.tech/tags/latency.md>), [linearizable](<https://devfeed.tech/tags/linearizable.md>), [pacelc](<https://devfeed.tech/tags/pacelc.md>), [replication](<https://devfeed.tech/tags/replication.md>), [semantics](<https://devfeed.tech/tags/semantics.md>), [system-design](<https://devfeed.tech/tags/system-design.md>)

## AI overview

This article explains how Azure Cosmos DB uses five consistency levels to expose PACELC trade-offs between consistency, availability, latency, and read freshness. It describes Strong consistency, bounded staleness, and Session consistency, including their operational trade-offs and suitable use cases.

## Source excerpt

Cosmos DB exposes the PACELC trade-off as five explicit levels instead of forcing a strong-or-eventual choice. Strong gives linearizable reads at the cost of write latency and availability. Session, the practical default for user-facing apps, gives read-your-writes within a session via per-partition session tokens while staying highly available.