Skip to content

Commit 294f60d

Browse files
authored
Update consistency-levels.md
Adding some details to other consistency levels also.
1 parent 7ea293f commit 294f60d

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/cosmos-db/consistency-levels.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -130,7 +130,9 @@ The following graphic illustrates the consistency prefix consistency with musica
130130

131131
### Eventual consistency
132132

133-
In eventual consistency, there's no ordering guarantee for reads. In the absence of any further writes, the replicas eventually converge.
133+
Like all consistency levels weaker than Strong, writes are replicated to a minimum of three replicas (in a four replica set) in the local region, with asynchronous replication to all other regions.
134+
135+
In Eventual consistency, the client will issue read requests against any one of the four replicas in the specified region. This replica may be lagging and could return stale or no data.
134136

135137
Eventual consistency is the weakest form of consistency because a client may read the values that are older than the ones it had read before. Eventual consistency is ideal where the application does not require any ordering guarantees. Examples include count of Retweets, Likes, or non-threaded comments. The following graphic illustrates the eventual consistency with musical notes.
136138

0 commit comments

Comments
 (0)