Eventually consistent

By Werner Vogels. CACM, 2008

1,237 citations recorded by the source corpus.

Subfields: Computer Networks and Communications, Information Systems

View Paper: https://www.semanticscholar.org/paper/77bed6d9e22344a11e931b7c86103006065c46bc

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Computer Networks and Communications

In Information Systems

Citations in the corpus

DepSky: dependable and secure storage in a cloud-of-clouds (2011, background): “However, several clouds do not ensure this guarantee, but instead provide read-after-write or eventual consistency [Vogels 2009] for the data stored (e.g., Amazon S3 [Ama 2010]).”
PNUTS: Yahoo!'s hosted data serving platform (2008, background): “However , there is a tradeoff between performance and availability on the one hand and consistency on the other, and it has repeatedly been observed that supporting general serializable transactions over a globally-replicated and distributed system is very expensive [17] [2] [1].”
A Survey of Large Scale Data Management Approaches in Cloud Environments (2011, background): “In particular, SimpleDB supports two read consistency options: eventually consistent read [35] and consistent read.”
Digital ecosystems in the clouds: Towards community cloud computing (2009, methodology): “Other directions of research include relaxing these properties to maximise concurrency [90].”
An evaluation of alternative architectures for transaction processing in the cloud (2010, background): “Unlike MySQL Replication, however, it does not synchronize concurrent read and write accesses to different copies of the same data so that it only supports a low level of consistency called eventual consistency [29].”
Conflict-Free Replicated Data Types (2011, background): “When network delays are large or partitioning is an issue, as in delay-tolerant networks, disconnected operation, cloud computing, or P2P systems, eventual consistency promises better availability and performance [17,21].”
Security and Privacy on Blockchain (2019, background): “Thus, data getting consistent eventually means that (1) it will take time for updates to be propagated to other replicas; and (2) if someone reads from a replica which is not updated yet (since replicas are updated eventually), then there is some risk of returning stale data [89].”
TAO: Facebook's Distributed Data Store for the Social Graph (2013, background): “TAO provides eventual consistency [33, 35] by asynchronously sending cache maintenance messages from the leader to the followers.”
Running Smart Grid Control Software on Cloud Computing Architectures (2011, background): “4) has been used to justify a number of weak guarantees [31][37].”
A comprehensive study of Convergent and Commutative Replicated Data Types (2011, background): “With the explosive growth of peer-to-peer, edge computing, grid and cloud systems, eventual consistency has become an urgent issue for the industry [5, 41].”