Blog Category: Multimaster 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.

How to build a multi-region, multi-master MySQL cloud database back- end capable of serving a global, high-volume cloud contact center: this global SaaS provider is a Cloud Contact Center solution provider, who needs to deliver up-to-date data to clients as quickly as possible.

This use case of a global SaaS provider looks at how our customer migrated from Amazon RDS to a truly global, geo-distributed multi-master Tungsten Clustering solution.

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?

This use case blog discusses a Telco provider that specializes in roaming, i.e. complete connectivity solutions around the world. It is our third ‘multi-master MySQL’ blog in our Continuent MySQL Use Case series.

For this next ‘multi-master MySQL’ blog in our Continuent MySQL Use Case series, we’re focussing on Financial Services Saas providers.

This next blog in our Continuent MySQL Use Case series is a sub-series on the topic of ‘multi-master MySQL’, in which we cover three multi-master MySQL use cases focusing on e-commerce to start with, financial services and telecommunications.

Why does the DIY approach fail to deliver vs. the Tungsten Clustering solution for geo-distributed MySQL multimaster deployments? Before we dive into the 10 reasons, note why commercially-supported enterprise software is less risky and in fact less costly.

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.

This blog explains why the Tungsten rollback error exists and why it's important.

In this blog post we will discuss how the managed cross-site replication streams work in a Composite Multi-Master Tungsten Cluster for MySQL, MariaDB and Percona Server.