This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note

Page References

Incoming links Outgoing links
Eventual consistency
Eventual consistency

Version management

Difference between version and

At line 1 added 16 lines
!!! Overview
[{$pagename}] is a [consistency] model used in [distributed Data Store] to achieve high [availability] that informally guarantees that, if no new updates are made to a given [data] item, eventually all accesses to that item will return the last updated value.
[{$pagename}] is widely deployed in [distributed Data Stores], often under the moniker of [Optimistic replication], and has origins in early mobile computing projects.
A system that has achieved [{$pagename}] is often said to have converged, or achieved [replica convergence] or reach a consistent [state]
[{$pagename}] is a weak guarantee – most stronger models, like linearizability are trivially eventually [consistent|Consistency], but a system that is merely [{$pagename}] does not usually fulfill these stronger constraints.
[{$pagename}] services are often classified as providing [BASE] ([Basically Available Soft state Eventual consistency]) semantics, in contrast to traditional [ACID] ([Atomicity], [Consistency], [Isolation], [Durability]) guarantees.
[{$pagename}] is sometimes criticized as increasing the complexity of distributed software applications. This is partly because [{$pagename}] is purely a liveness guarantee (reads eventually return the same value) and does not make safety guarantees: an [{$pagename}] system can return any value before it has achieved [replica convergence].
!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthorTop