Blog Category: MySQL High Availability

Watch this on-demand webinar to learn the right way to deploy geo-distributed databases. We look at the pitfalls of deploying a single site and passive sites, and from there we show how to provide the best user experience by leveraging geo-distributed MySQL.

Watch our latest on-demand webinar: Deploying Hybrid & Multi-Cloud Applications With Ultimate MySQL Availability. Learn about the pros and cons of single cloud region vs multi-region cloud deployments … and more.

We’ve been receiving requests recently from MySQL users wanting to understand how InnoDB Cluster compares to Tungsten Clustering, our MySQL HA, disaster recovery, and geo-clustering solution. In response we have come up with this comparative outline, looking at some of the key features of each.

This blog discusses some best practices for using multiple filesystems on MySQL database servers and how to achieve the best performance with them, while avoiding some of the possible pitfalls.

Do-it-Yourself (DIY), database migration; what other approaches are there to challenges of MySQL availability, reliability, scalability and application performance?

Continuent Tungsten enables greater application availability and performance especially across WAN, it saves tons of manual labor and headache, it’s backed by premium 24/7/365 support, and it enables all sorts of new freedom and possibilities for data infrastructure including multi-cloud, hybrid-cloud, and advanced, real-time analytics.

This blog explores the best practices for deploying Tungsten Clustering for MySQL across Availability Zones, outlining the approaches for best high availability, fast response times, and load balancing recommendations.

People approach Continuent for many reasons, including: MySQL Continuous Operations: their business is using MySQL for business-critical applications that require zero downtime, including for maintenance updates MySQL Performance: their application performance and user experience are suffering due to a faltering MySQL backend

An overview of a Tungsten topology that doesn’t get much attention: the Cluster-Slave, which is an easy way to get data resiliency and integration, with features that make it ideal for big data analytics, reporting, and backups.

This MySQL high availability and disaster recovery use case is based on a customer of ours who is a government-regulated lottery service and who needs 24x7x365 operations as well as be able to perform maintenance without any disruption to their public facing gaming website.

Version 6+ of Tungsten Clustering comes with a host of improvements for your Multi-Site Multi-Master topology (MSMM); this is partly why it has a new name: Composite Master-Master (CMM). Probably the most notable improvement is that the Managers are more aware. What does that mean?

In this MySQL Use Case blog we look at a customer of ours who were able to grow their SaaS business from tens of customers to thousands of enterprise customers once they achieved continuous MySQL operations with Continuent Tungsten.

This is the second post in a series of MySQL use case blogs. It discusses a SaaS provider dealing with sensitive medical data and their need to be able to quickly deploy clusters in AWS and recover from multi-zone AWS outages.