Read Replicas and the Problem of Stale Reads
A user saves a change, then a subsequent read from a replica appears to undo it. This guide gives you a small, testable way to approach the issue before changing a live system.
A practical workflow
- Identify flows requiring read-after-write consistency and route those reads to the primary when needed.
- Measure replication lag and test behavior during failover and temporary disconnection.
What to check
A replica helps read capacity and availability planning, but it is not a backup against accidental deletion. Compare the result with the original problem and record what changed. If a measurement or test does not support the change, revisit the assumption rather than adding more complexity.
Keep the experiment small enough to reverse. Document the starting state, the change and the result so another person can repeat the process. Product menus and versions can change, so check the current documentation for your environment.
Official reference: Read the documentation.