liveBook · Manning

Read-your-writes

As explained in ScyllaDB in Action

Read-your-writes consistency is a consistency guarantee that a client’s later reads reflect its completed writes.

Read-your-writes consistency guarantees that a client’s later reads reflect its completed writes. In ScyllaDB, QUORUM consistency for both reads and writes provides this behavior and prevents queries from accessing stale data. section 8.2.2

Choose a consistency level according to the balance between consistency, availability, and cluster load:

  • Use QUORUM for reads and writes when clients should read recently written data and tolerate the loss of at least one node with replication factor 3. section 8.2.2
  • Use ONE for reads when lower cluster load matters and the application can tolerate potentially stale data. section 8.2.2
  • Use LOCAL_QUORUM or EACH_QUORUM to control whether quorum obligations apply within one datacenter or across every datacenter. section 8.2.2

How ScyllaDB in Action covers it

How deep it goes
Defines the guarantee, recommends QUORUM reads and writes, and contrasts ONE with datacenter-specific quorum variants.
Examples
Uses QUORUM reads and writes, ONE reads, replication factor 3, and LOCAL_QUORUM or EACH_QUORUM comparisons.
What you can do after
Apply ScyllaDB consistency levels to obtain fresh reads or deliberately accept possible staleness.
How it connects
Connects read-your-writes consistency with QUORUM consistency, replication factor, stale reads, availability, and datacenters.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of ScyllaDB in Action. The section links point to the parts of the book it draws on.