Multi-AZ vs Single-AZ Trade-offs
What you'll learn: How to weigh the cost, performance, and durability differences between Single-AZ and Multi-AZ database deployments.
Understanding the Trade-offs
When you deploy a managed database like RDS, you choose between Single-AZ (one Availability Zone) or Multi-AZ (multiple Availability Zones). This decision impacts three key dimensions: cost, performance, and durability.
Cost Considerations
Single-AZ is cheaper because you're running one database instance in one location. You pay for one instance, one set of storage, and minimal data transfer.
Multi-AZ roughly doubles your cost. You're paying for a standby replica in another AZ, synchronous replication between zones, and cross-AZ data transfer fees. Think of it like paying for a backup generator that's always running.
Performance Trade-offs
Single-AZ has slightly lower write latency because data only writes to one location.
Multi-AZ adds a small synchronous replication delay (typically milliseconds) because each write must be confirmed by the standby before completing. Read performance stays the same—you still read from the primary. The standby is not used for read traffic in standard Multi-AZ.
Durability and Availability
Single-AZ is vulnerable to AZ-level failures. If that AZ has an outage, your database is unavailable until recovery.
Multi-AZ provides automatic failover to the standby in another AZ during outages, hardware failures, or maintenance. Downtime typically ranges from 60-120 seconds instead of hours. Your data survives even if an entire datacenter fails.
When to Choose Which
Use Single-AZ for dev/test environments, non-critical workloads, or when budget is extremely tight. Use Multi-AZ for production databases where availability and data durability justify the added cost.
Key Takeaway: Multi-AZ roughly doubles database costs and adds minor write latency, but provides automatic failover and protection against AZ failures—essential for production workloads where downtime is costly.