Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
These are the consistency levels supported by the Azure Cosmos DB service.
public enum ConsistencyLevel
type ConsistencyLevel =
Public Enum ConsistencyLevel
Bounded Staleness guarantees that reads are not too out-of-date. This can be configured based on number of operations (MaxStalenessPrefix) or time (MaxStalenessIntervalInSeconds). For more information on MaxStalenessPrefix and MaxStalenessIntervalInSeconds, please see ConsistencyPolicy.
ConsistentPrefix Consistency guarantees that reads will return some prefix of all writes with no gaps. All writes will be eventually be available for reads.
Eventual Consistency guarantees that reads will return a subset of writes. All writes will be eventually be available for reads.
Session Consistency guarantees monotonic reads (you never read old data, then new, then old again), monotonic writes (writes are ordered) and read your writes (your writes are immediately visible to your reads) within any single session.
Strong Consistency guarantees that read operations always return the value that was last written.
The requested Consistency Level must match or be weaker than that provisioned for the database account. For more information on consistency levels, please see Consistency Levels article.
Submit and view feedback for