Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Current »

Consistency Models

Strong Consistency

any read operation returns a value corresponding to the result of the most updated write data item. A client never sees out-of-date data.

Weak Consistency

subsequent read operations may not see the most updated value.

Eventual Consistency

this is a specific form of weak consistency. all updates are propagated and all replicas are consistent.

Strong Consistency is achieved by forcing a replica not to accept new reads/writes until every replica has agreed on current write. This could block new operations.

Eventual consistency is the recommended model for a KV store.

  • No labels