Multiple ChoiceIntermediate 45s
Eventual consistency read path
A user updates their profile, then immediately reloads the page backed by a lagging read replica. What is the best architectural mitigation?
Options
- 1Return the write to the client and have the client echo it locally (read-your-writes token or local optimistic state)
- 2Switch the whole system to strong consistency everywhere by disabling read replicas in the cluster entirely
- 3Block the page load until every replica has caught up, for all users, before rendering anything at all
- 4Cache the user's profile response forever on the client so the replica lag is never visible to anyone
Think you can answer under pressure?
Get matched and answer live questions in 3-minute 1v1 battles. Elo ranking, badge tiers and bragging rights on the line.