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.
On this page
Concept Made Simple
Coffee Chat Question
“Multi-AZ vs read replicas in RDS — what does each solve?”
Remember It Faster
Mind Map Answer
- Multi-AZ
- sync standby, auto-failover, HA
- Read replica
- async copies, scale reads
- Standby
- serves NO traffic (just failover)
- Combine
- Multi-AZ + replicas for HA + read scale
Think Beyond the Expected
What If?
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:
- Multi-AZ = HA/sync/failover
- standby serves no traffic
- read replicas = async read scaling
- replica lag/eventual consistency
- combine both
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
- How does replica lag affect read-after-write?
- Cross-Region read replicas — use case?
- How does Aurora differ (shared storage)?
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?
Affiliate links
Tools for Your Developer Workspace
Equipment for a comfortable, productive setup.
As an Amazon Associate I earn from qualifying purchases.
- MonitorView on Amazon : BenQ EW2790U 27-inch Monitor (opens in a new tab)
BenQ EW2790U 27-inch Monitor
- LaptopView on Amazon : Acer Aspire One Laptop (opens in a new tab)
Acer Aspire One Laptop
- Office ChairView on Amazon : Wakefit Gravita Ergonomic Office Chair (opens in a new tab)
Wakefit Gravita Ergonomic Office Chair