How the Continuent Proxy selects database cluster nodes for executing read operations.
How the Continuent Proxy selects database cluster nodes for executing read operations.
This is the next blog in our ‘High Noon’ 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 Google Cloud (GCP) for MySQL as compared to MySQL, MariaDB clusters with Continuent Tungsten, the only complete, fully-integrated clustering solution for MySQL - on-premises, in the cloud, hybrid-cloud or multi-cloud.
This blog was written in response to a question about the differences between a 3-node MySQL cluster and a 2-node-plus-a-witness MySQL cluster for MySQL high availability (HA).
This blog discusses Asynchronous versus Synchronous MySQL replication for MySQL clustering. Synchronous replication is viewed as the ‘holy grail’ of clustering. But unfortunately, when something is too good to be true, it often is. Before the Tungsten cluster solution Continuent built two synchronous replication cluster solutions (m/cluster, uni/cluster), but we abandoned those for good reasons.
What is the difference between MySQL replication and MySQL clustering? While clustering involves a layer of replication, the capabilities, benefits, and reasons for using clustering versus replication are very different. At Continuent, we offer both clustering and replication for your MySQL, MariaDB, and Percona MySQL - in the cloud, on-prem, hybrid-cloud and multi-cloud, with no application changes or downtime necessary.
“We don’t take backups, we use replication instead.” If you happen to agree with this statement, I urge you to continue reading. But even if you think you have a good backup plan, I still urge you to continue reading. Taking backups is usually not one of the most exciting parts of the job, but it might be the part that saves your company from a catastrophe. So, let’s make a plan!
Disaster Recovery for Continuous MySQL Operations does not have to be hard, but it does have to be WAN: Multi-Site, Hybrid-Cloud, Multi-Cloud. This blog discusses Business Continuity, Disaster Recovery, or “DR,” and an overlooked clustering feature that makes continuous database operations easy, affordable, and manageable.
There are a number of MySQL HA solutions around. But there are surprisingly few MySQL DR solutions. And there is only one solution that Does MySQL DR Right!
There are a number of MySQL HA solutions around. But there really is only one solution that Does MySQL HA Right!
Now available on demand: Watch the Continuent Tungsten MySQL Use Case Webinar Series for 2020 with Eero Teerikorpi, Founder & CEO of Continuent.
Watch the replay of this Zero Downtime MySQL use case webinar with Continuent CEO Eero Teerikorpi and find out how Kentucky Lottery achieved continuous MySQL operations with high availability, data protection, and disaster recovery using a Composite Active/Passive Tungsten Clustering Topology.
Join the replay of this webinar which discusses the use of geo-distributed active/active MySQL clusters for Telco providers, and on how to cost-effectively provide worldwide mobile roaming access with cloud-based Tungsten MySQL clusters.