The Twitter fail whale never made a dime. For big e-commerce sites, downtime can costs thousands to millions of dollars. Services architectures have baked lots of resiliency into apps, but databases and their system of record design are vulnerable to be single points of failure for entire systems.
Smart DBAs have developed a myriad of strategies to minimize downtime, with replication and redundant hardware. Usually these systems involve some manual intervention and downtime as failover protocols take hold. Also, these strategies are expensive.
At Clustrix, we think these strategies are a poor fit for modern apps. They are expensive in the cloud, and complex in practice. So, we built a drop-in MySQL database that makes high availability simple and cost-effective in the cloud. It is so simple that ClustrixDB can be configured to sustain n number of node failures at any time with a simple parameter change. That’s right, you pick the number of nodes that can fail, and ClustrixDB makes it happen gracefully.
To learn more about how we think of high availability in MySQL deployments, join us for this webinar where we will discuss:
- How do you achieve high availability with MySQL?
- Is my MySQL high availability strategy cost effective?
- When is it time to replace MySQL with something else?
- How is it possible to survive a multi-node failure in MySQL?
Click on the other installments below to register.
Fill out the form below to register for Part 4 of this Tech Talk Series.
About the Presenter
Dave Anselmi is Director of Product Management at Clustrix and brings over 18 years of product management, integration, and project management experience in database technology and e-commerce.
He’s very excited to be at the forefront of pushing the limits of linear scale-out ACID-compliant relational database technology with our clustered database, ClustrixDB.