Be the first to like this
For high-value, high-throughput sites, downtime can cost hundreds of thousands to millions of dollars. Service architectures have baked lots of resiliency into apps, but databases and their system of record design are often vulnerable to single points of failure, bringing down entire systems. Worse still, when the database is recovered, there can be missing data. How many database transactions can your workload handle losing if your primary database goes down?
There are many strategies to minimize MySQL downtime, usually using replication and redundant hardware. Often these systems involve some manual intervention and potential downtime as failover protocols take hold. Also, these strategies may be expensive and require redundant hardware.
At Clustrix, we think there are alternative strategies that may be a better fit for modern apps in a MySQL environment.
In our final Tech Talk in this series on scaling MySQL, we evaluate multiple HA strategies. We also discuss the following topics:
- The difference between fault tolerance and high availability
- Best practices for achieving high availability with MySQL
- What are the costs of achieving HA? What can be the most cost-effective strategy?
- How is it possible to survive a multi-node failure in MySQL?
View the webcast of this Tech Talk on our YouTube channel.