Looking at the prices for RDS instances, the multi-AZ instances cost double. Having a production environment in mind, does it worth it?
What uptime should I expect from a single-AZ instance, as opposed to a multi-AZ one? Has anyone had experience running a production DB on both single and multi availability zones?
When you change your Single-AZ instance to Multi-AZ, you don't experience any downtime on the instance. During the modification, Amazon RDS creates a snapshot of the instance's volumes. Then, this snapshot is used to create new volumes in another Availability Zone.
Increase availability Use Amazon RDS Multi-AZ synchronous replication technologies to keep data on your standby database instance up to date with the primary. Enhance availability by deploying a standby instance in a second AZ, and achieve fault tolerance in the event of an AZ or database instance failure.
Benefits of Read Replica Read Replica helps in decreasing load on the primary DB by serving read-only traffic. A Read Replica can be manually promoted as a standalone database instance. You can create Read Replicas within AZ, Cross-AZ or Cross-Region.
Change from Multi-AZ to Single-AZ using the --no-multi-az option.
We have a multi-AZ production deployment with AWS RDS and it's been working fabulously well for the last 3 years.
The multi-AZ catalog page clearly lists out the benefit of using a multi-az vs single RDS deployment. One of the most important aspects of running multi-az is the fact that if one of the AZ in a region goes down, the production application traffic is automatically routed to the RDS in the alternate AZ. Also, DB maintenance and upgrades are applied to the RDS per AZ basis (for a multi-AZ RDS) without impacting uptime.
With respect to cost, it is totally up to the nature of the application as to how much is the degree of downtime tolerance that it can sustain. It's a cost vs uptime trade-off.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With