Nehir
How do I handle read-after-write when replication lag hides a user's own just-written data?
Route a user's reads to the primary for a few seconds after their write, and reach for LSN fencing only if that window isn't precise enough.
Tag
Transaction boundaries, isolation levels and locking: what consistency costs. questions under this tag, answered directly.
1 answered questions carry this tag.
Route a user's reads to the primary for a few seconds after their write, and reach for LSN fencing only if that window isn't precise enough.