✳flâneur — a map of the web's best reading

Read-your-write consistency

arpitbhayani.me · 1,368 words · saved by 1 readers

The most common way to scale the reads hitting a distributed data store is by adding Read Replicas. These replicas handle all the reads of the systems freeing up the Master to deal with the writes. Although Replicas do help us scale, it brings a new set of problems; and in this essay, we discuss one such issue, called “Read-your-write” consistency, and look at possible solutions. In a Master-Replica setup, the Writes happening on the Master take some time to reach the Replica. This delay in propagation is called Replication Lag. If a client has made a Write and is immediately trying to read the written item, this read may go to the Read Replica that is yet to sync with the Master. When the client issues the Read on a Replica that has yet to receive the write, it leads to an undesirable behavior wherein the client will see the old value (or null) and think that the write it made was lost. Read-Your-Writes consistency states that the system guarantees that, once an item has been updated,

Read-Your-Writes Consistency Read-Your-Writes Consistency Arpit Bhayani engineering, databases, and systems. always building. The most common way to scale the reads hitting a distributed data store is by adding Read Replicas . These replicas handle all the reads of the systems freeing up the Master to deal with the writes. Although Replicas do help us scale, it brings a new set of problems; and in this essay, we discuss one such issue, called “Read-your-write” consistency, and look at possible solutions. The Problem In a Master-Replica setup, the Writes happening on the Master take some time t

Explore this link on the map →

related reading