Replication · Fill in the blank

A user sees a new comment, refreshes, and it is gone, because the second read went to a replica further behind. The guarantee that prevents this is blank.

medium Consistency

Answer

A user sees a new comment, refreshes, and it is gone, because the second read went to a replica further behind. The guarantee that prevents this is monotonic reads.

Also accepted: monotonic read, monotonic-read for monotonic reads.

Why

A simple fix is to route each user's reads to the same replica (for example by hashing the user id), so time never appears to move backwards for them.

Review this in your daily deck All cards in Replication