Multiple ChoiceBeginner 45s
Read-your-writes routing
A user updates their profile then immediately reloads and sees stale data. The service reads from a lagging replica. Which fix best provides read-your-writes for that user?
Options
- 1Increase the number of read replicas, so at least one is guaranteed to have applied the user's recent write before the next read
- 2Route the user's subsequent reads to the primary or a replica known to have caught up past the write's LSN
- 3Disable caching entirely on the read path, so every request is forced to reach a node that already reflects the user's write
- 4Use a shorter connection timeout on the read path, so stale replica responses are abandoned and retried until one returns fresh data
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.