How do read replicas help, and what bug do they introduce for a user who just posted?
PICTURE THIS: 1, 2, 2, 8
Simple meaning
Replicas take SELECT load off the primary.
WHY — SQL instead of guessing?
Why interviewers care about SQL:
question about SQL.
trade-offs, and what you would actually do on a Backend project - not buzzwords.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1Replicas take SELECT load
off the primary.
- 2Replication lag means a
follow-up GET can miss the row the user just created.
- 3Send reads-your-writes to the
primary, use a lag-aware router, or wait on a commit timestamp before reading a replica.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
Replicas take SELECT load off the primary. Replication lag means a follow-up GET can miss the row the user just created.