When evaluating a solution, we need to define the requirements for our application around these following elements:
- High Availability (HA): Local fast and automatic failover, for high availability
- Disaster Recovery (DR): Remote fast and site level failover, for disaster recovery and continuous operations
- Zero Downtime: Perform complex system changes or routine maintenance, while keeping applications available
- Geo-Scale: Geographically distributed (active/passive or active/active) low-latency database deployments with a single consolidated management view
- Read Scale: Fast local response times for read traffic, even in a geo-distributed deployment
- Multi-Primary: Ability to deploy active MySQL clusters across multiple regions
- Transparency: No changes to application code or stack
- Flexibility: Avoid cloud or vendor lock-in
- Support: Access to 24/7 support by experienced MySQL database engineers
Welcome to the next blog in the “Continuent High Noon Series!” We are looking at the various solutions for MySQL that provide High Availability (HA), Disaster Recovery (DR), and Geo-Scale deployments. We will dig into the requirements, features, and limitations of each solution, then rate them on such topics as performance, scalability, failover, and more!
ClusterControl helps deploy open source solutions, and for HA the more relevant deployment is Galera Cluster. So underlying Clustercontrol is the same technology that we already discussed, described here in this Galera comparison page. (For more information on the different types of replication for clustering, check out this blog about the different types of replication used in MySQL clustering.)
Some of the notable features are:
- Deploy various databases and clusters, along with all prerequisites in an easy to use point and click interface
- Management deployed databases and clusters through the GUI interface
- Variety of in depth monitoring and alerting available, with easy to configure graphs
ClusterControl Cross-Region Requirements
ClusterControl itself has minimal requirements, however there are requirements for the underlying topology that will be deployed by ClusterControl. Typically clusters deployed over a WAN use asynchronous replication, which is loosely coupled between sites. Having any sort of synchronous replication solution deploy across a WAN is not practical due to lag and increased latency in the application. In the case of a multi-region deployment with ClusterControl, you must use an asynchronous solution to join the clusters. This of course makes cluster management much more difficult due to mixing of technologies.
The limitations stem from having to deploy technologies that do not easily support multi-site topologies. And while ClusterControl can also deploy ProxySQL, the end result is having a deployment consisting of multiple technologies, instead of having a multi-site deployment using one product out of the box.
Tungsten Cluster vs ClusterControl
Continuent Tungsten Clustering is all about geo-distributed MySQL high availability on-premises, hybrid-cloud, and multi-cloud. Our customers stay with us (current average life-time 8+ years and counting), citing the completeness and maturity of the solution and the excellent, very fast (less than 3 minutes average response time) 24/7 support as reasons to choose Continuent.
As part of our High Noon series of on-demand webinars, this webinar looks at some of the key characteristics of ClusterControl and how it fares when compared to Continuent Tungsten Clustering.
Watch this webinar to learn about how to best build a geo-scale, multi-region and highly available MySQL, MariaDB, or Percona MySQL backend, in the cloud, hybrid-cloud, multi-cloud, or on-premises.
Reach out to see if Tungsten Clustering is a better fit than ClusterControl for your requirements and environment!
We’ve recently introduced this new High Noon series to help demonstrate how and why customers with business-critical or mission-critical MySQL applications have grown for years with Tungsten Clustering and continue to choose it versus alternatives.