IntermediateScenario
10 min
Read-After-Write Inconsistency
ConsistencyCachingDatabases
Advertisement
Interview Question
Users report that data they just wrote is not visible when reading immediately. Outline your investigation and mitigation.
Key Points to Cover
- Identify eventual consistency in DB/replicas or caches
- Check replication lag and cache invalidation
- Use read-your-writes/session consistency or stickiness
- Adjust TTLs and invalidate/write-through on updates
- Measure and alert on replication/caching delays
Evaluation Rubric
Diagnoses consistency model correctly30% weight
Handles caches/replication properly30% weight
Implements read-your-writes strategies20% weight
Adds metrics/alerts on lag20% weight
Hints
- 💡Sticky reads or session tokens help.
Potential Follow-up Questions
- ❓When to use quorum reads?
- ❓What about dual writes?
Advertisement