What is the difference between Multi-AZ and Read Replicas in RDS?
Understand the difference between RDS Multi-AZ high availability and Read Replicas for read scaling, including replication, failover, and when to combine them.
Expected Interview Answer
Multi-AZ is a high-availability feature that keeps a synchronous standby copy of your RDS database in another Availability Zone for automatic failover, while Read Replicas are asynchronous copies used to scale read traffic.
A Multi-AZ standby is not readable and exists purely for durability and failover; if the primary fails, RDS automatically promotes the standby and updates the DNS endpoint. Read Replicas, by contrast, are readable endpoints kept in sync asynchronously, so they can lag behind and are used to offload SELECT-heavy workloads or reporting. The two solve different problems and are often combined for both availability and scalability.
- Multi-AZ gives automatic failover with no data loss (synchronous)
- Multi-AZ standby improves durability across Availability Zones
- Read Replicas scale read throughput horizontally
- Read Replicas can be promoted to standalone databases
- Read Replicas can span regions for disaster recovery
- They can be combined for both HA and read scaling
AI Mentor Explanation
Multi-AZ is like a fully padded twelfth man ready to walk out the instant a batter is injured, but who never bats until then. Read Replicas are more like extra net bowlers who let many batters practice at once. One is standby insurance; the other multiplies capacity — the same split RDS makes between failover and read scaling.
Step-by-Step Explanation
Step 1
Identify the goal
Decide whether you need high availability (Multi-AZ) or read scaling (Read Replicas).
Step 2
Enable Multi-AZ
Turn on Multi-AZ so RDS provisions a synchronous standby in a second Availability Zone.
Step 3
Understand failover
On primary failure, RDS promotes the standby and repoints the DNS endpoint automatically.
Step 4
Add Read Replicas
Create asynchronous replicas and direct read-only queries to their separate endpoints.
Step 5
Combine both
Use Multi-AZ for resilience and Read Replicas for scaling, optionally promoting a replica for DR.
What Interviewer Expects
- Synchronous standby vs asynchronous replica
- Multi-AZ standby is not readable
- Automatic failover and DNS endpoint switch
- Read Replicas scale reads and can lag
- How the two can be combined
Common Mistakes
- Claiming you can read from a Multi-AZ standby
- Thinking Read Replicas provide automatic failover
- Confusing synchronous with asynchronous replication
- Believing Multi-AZ scales read throughput
- Ignoring replica lag in consistency-sensitive apps
Best Answer (HR Friendly)
“Multi-AZ keeps a hidden backup copy of your database ready to take over instantly if the main one fails, protecting against downtime. Read Replicas are extra readable copies that share the load of read-heavy traffic so the main database stays fast.”
Code Example
# Convert an existing database to Multi-AZ for high availability
aws rds modify-db-instance \
--db-instance-identifier prod-db \
--multi-az \
--apply-immediately
# Create a Read Replica to offload read traffic
aws rds create-db-instance-read-replica \
--db-instance-identifier prod-db-read-1 \
--source-db-instance-identifier prod-dbFollow-up Questions
- How does RDS handle failover time in a Multi-AZ deployment?
- Can a Read Replica be promoted to a standalone database?
- What is replica lag and how do you monitor it?
- How does Aurora's storage architecture change this comparison?
MCQ Practice
1. Which statement about a Multi-AZ standby is true?
The Multi-AZ standby is a synchronous copy used only for failover; it cannot serve reads.
2. What is the primary use of an RDS Read Replica?
Read Replicas are asynchronous readable copies used to offload and scale read-heavy workloads.
Flash Cards
Is a Multi-AZ standby readable? — No, it exists only for automatic failover and durability.
What replication does Multi-AZ use? — Synchronous replication to a standby in another Availability Zone.
What replication do Read Replicas use? — Asynchronous replication, so they may lag behind the primary.
Can a Read Replica become standalone? — Yes, it can be promoted to an independent writable database.