RDS Multi-AZ vs Read Replicas
Reviewed by Gurusankar M. · Updated Aug 24, 2026
⚡ Short Answer
Multi-AZ is for HA/failover: a synchronous standby in another AZ that auto-promotes on failure (not for read scaling — the standby serves no traffic). Read replicas are for read scaling: asynchronous copies you route read queries to (eventually consistent, can be cross-Region). They solve different problems and are often combined.
☕Coffee Chat Question
Concept Made Simple
“Multi-AZ vs read replicas in RDS — what does each solve?”
🧠Mind Map Answer
Remember It Faster
🔥What If?
Think Beyond the Expected
A team adds Multi-AZ hoping to offload read traffic and sees no improvement — why?
Multi-AZ's standby is passive — it exists only for failover and serves zero queries. To scale reads you need read replicas (which you explicitly route SELECTs to). Multi-AZ = availability; read replicas = read throughput. They're different tools.
😂Real World
Confusing Multi-AZ (HA) with read replicas (read scaling) is a common misconception; production DBs use Multi-AZ for failover and add read replicas when read load grows.
🎯Interviewer's Expectation
Keywords they're listening for:
⚠️Common Mistakes
- ✗Expecting Multi-AZ standby to serve reads
- ✗Reading from a lagging replica for read-after-write
- ✗Single-AZ production databases
✅Best Practices
- ✓Multi-AZ for HA; read replicas for read scale
- ✓Handle replica lag in read-after-write flows
- ✓Consider Aurora for scale + HA
🔁Follow-up Questions
- 1How does replica lag affect read-after-write?
- 2Cross-Region read replicas — use case?
- 3How does Aurora differ (shared storage)?
🧩Related Technologies
Continue Learning with AI
Take this question deeper with your favourite AI assistant. Pick a depth, copy the prompt, or open it directly — AI is your learning companion, not a shortcut.
Plain-language foundations
I'm preparing for a software engineering interview and want to understand this from scratch, as a beginner. Topic: DynamoDB (AWS) Interview question: "Multi-AZ vs read replicas in RDS — what does each solve?" Please: 1. Explain the core idea in simple, plain language, using an everyday analogy. 2. Define any technical terms you use. 3. Walk through one small, concrete example. 4. Finish with a single sentence I can easily remember. Keep the tone friendly and assume I'm new to this topic.
Was this answer helpful?
⭐ Featured Products
Support our platform by exploring our recommended products.
As an Amazon affiliate, purchases through these links may earn us a small commission — at no extra cost to you. It helps keep Full Stack Interview Guru free.