0:00
/
0:00

System Design : Read after write consistency explained

System design is a lie sometimes.

You perform a WRITE operation on a distributed system. The API returns a successful response.

Seconds later, you perform a READ operation, but the data is gone. It's not there!

You start debugging, thinking you're crazy.

This is a consistency nightmare.

Read-after-write consistency is the guarantee that any READ request for an object will return the latest WRITE to that same object.

Explained this like you are 5, watch👇

Discussion about this video