Eventual Consistency
Subject: Computer and Technology noun /ɪˈvɛn.tʃu.əl kənˈsɪs.tən.si/ 1 definition
- distributed-systems
- consistency-models
- data-replication
- database-architecture
-
Definition (noun)
Entry #229 · UpdatedEventual Consistency is a weak consistency model used in distributed systems that prioritizes high availability and low latency over immediate synchronization across replicas. Instead of requiring reads and writes to reflect the single latest global state immediately, the system propagates updates asynchronously and guarantees that, if no new updates are made to a data item, all replicas will eventually converge to the same value. Because it places no strict upper bound on replication delay, applications using this model must tolerate temporary stale reads and employ conflict resolution when concurrent writes occur.
Common Forms
Strong Eventual Consistency (SEC): Guarantees that any two replicas that have received the same unordered set of updates hold identical states without extra coordination or rollbacks, commonly implemented with Conflict-Free Replicated Data Types (CRDTs).
Read-Your-Writes Consistency: A session-level variation ensuring that a client always observes its own completed updates on subsequent reads—often using sticky routing or version tokens—while other clients may temporarily see older replicas.
Monotonic Read Consistency: Guarantees that once a client observes a given version of a data item, subsequent reads by that same client will never return an earlier version as requests hit different replicas.
Bounded Staleness: Constrains asynchronous replication by guaranteeing that replica reads lag behind the latest write by no more than a configured time interval or number of versions.
Example
When a user updates their display name on a globally distributed social platform, the write succeeds immediately on the nearest US-East replica while a follower querying a European replica milliseconds later still sees the old name. Once asynchronous replication finishes propagating the update across regions and no further edits occur, queries to every replica converge on the new display name.