Blog

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.

This is the first blog in our ‘High Noon’ comparison series in which we look at the alternative solutions for MySQL high availability, disaster recovery and geographic-distribution. We focus on highly available, geo-scale, multi-region MySQL for business critical applications as directly compared to Amazon Aurora. Tungsten Clustering makes it easy to deploy and manage highly available MySQL clusters with any version of MySQL, MariaDB, and Percona Server for MySQL on-premises, in the cloud, hybrid-cloud or multi-cloud.

Why do Continuent customers say year after year that Tungsten Clustering is a better MySQL HA/DR/Geo-Scale clustering and replication technology - in the cloud, on-prem, hybrid-cloud, multi-cloud - compared to alternatives such as Amazon Aurora for MySQL, Galera Cluster and host of others? We have put together a comprehensive comparison so you can learn about the pros and cons of various MySQL solutions for business-critical and mission-critical apps - and make an informed decision about what’s best for your needs and environment!

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.

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.

ProductIP has been a Continuent customer since November 2014 and is sharing its Continuent experience here: from initially setting up their infrastructure in Hong Kong to running a geographically distributed MySQL database replication and clustering environment with Continuent Tungsten, read about their journey with us in this guest post.

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!

This blog provides a refresher outline of what’s involved in our Tungsten Cluster Competitive Comparison program and Tungsten Cluster highlights as well. Read on and find out why Tungsten Cluster is a better and more cost-effective overall MySQL HA/DR/Geo-Scale solution compared to other options in the market.

This blog provides basic information about business-critical application to database connections; my team focuses on MySQL, MariaDB, and Percona Server for MySQL on Linux/Unix that’s infrastructure-agnostic (on-prem, VM, hybrid-cloud, cloud, multi-cloud, etc.).

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.

This month we’re celebrating our 4th - or is it our 20th? - anniversary: read about our history and where we are today on the path to more years of MySQL availability and continuous operations.

Find out why and how we replaced an AWS RDS/MySQL solution with a Tungsten Cluster composite active/active MySQL solution to offer a geo-distributed MySQL back-end for IoT services at Samsung.