Blog

This article explores some of the leading MySQL — also including MySQL variants MariaDB and Percona Server — high availability (HA) and disaster recovery (DR) solutions – in alphabetical order, including AWS Aurora, Continuent Tungsten, DIY MySQL clusters, Galera Cluster, and MySQL InnoDB Cluster.

In the current MySQL ecosystem, organizations must focus on high availability and fault tolerance to ensure business continuity and maintain customer trust. A recent inquiry to prominent tech executives identified five key themes for achieving this: multi-region deployment to prevent single points of failure, automated self-healing for quick issue resolution, redundancy through system duplication, microservices architecture for improved resilience, and load balancing for efficient resource management. Continuent's Tungsten Clustering solution aligns with these strategies, making it an optimal choice for organizations managing critical workloads.

Tungsten Clustering allows for many types of maintenance to happen with no downtime at all. This blog post will explore how to upgrade the actual MySQL Server on all cluster nodes with zero downtime. These same steps may be used to upgrade the MySQL server or patch the OS.

This post covers some standard Nagios checks that would help keep your Tungsten cluster nodes running MySQL / MariaDB / Percona Server healthy.

Your MySQL database cluster contains your most business-critical data; in this post, we discuss how to ensure proper performance under load.

In this blog post we explore various options for performance tuning MySQL server for better replica replication performance.

In this blog post we will define what a split-brain scenario means in a MySQL database cluster, and then explore how a Tungsten MySQL database cluster reacts to a split-brain situation.

In this blog post, we will discuss how to use the Tungsten Connector keep-alive feature to ensure long-running MySQL & MariaDB/Percona Server client sessions stay connected in a Tungsten Cluster.

It is always a good idea to be mindful of open ports on your hosts, since they can be used by bad actors to gain access to your systems. For this reason, it is often desirable to prevent outside connections to the port whenever possible to prevent intrusions. For security purposes (and possibly PCI compliance), the Tungsten Connector proxy has the ability to bind to localhost/127.0.0.1 instead of listening on all available IP addresses via 0.0.0.0.

One nice thing about Tungsten Clustering is that you need just a single command to move the primary role to another host in your cluster.

This is the next blog in our competitor comparison series in which we look at the main solutions for MySQL high availability, disaster recovery and geographic distribution. Here we focus on highly available, geo-scale, multi-region MySQL for mission-critical sites and apps with ClusterControl as compared to MySQL clusters with Continuent Tungsten, the only complete, fully-integrated clustering solution for MySQL - on-premises, in the cloud, hybrid-cloud or multi-cloud.

For the sixth in the Competitor Comparison series in which we look at the main solutions for MySQL high availability, disaster recovery and geographic distribution, I got a chance to interview Matt Lang, Customer Success Director, Americas at Continuent. We focused on highly available, geo-scale, multi-region MySQL for mission-critical sites and apps with Do-it-Yourself (DIY) solutions as compared to MySQL clustering with Continuent Tungsten, the only complete, fully-integrated clustering solution for MySQL - on-premises, in the cloud, hybrid-cloud or multi-cloud.