In this short post we will highlight the key differences between Multi-Site Active/Active (MSAA) and Composite Active/Active (CAA) topologies. The core principle behind an active/active topology is that you have more than one writable cluster. So why do we have more than one type of Active/Active topology?
For MySQL and MariaDB database clusters, Saas, Fintech and other organizations with mission-critical databases typically require what’s called a managed “composite” cluster, or “cluster-of-clusters.” This blog is about active/active versus active/passive composite clusters for MySQL and MariaDB database systems.
This blog is about troubleshooting failed DDL across all Replicas in a composite active/active (CAA) Tungsten Cluster. The issue was resolved by setting a more permissive SQL_MODE, then locating and cleaning the bad data with proper NULLs before re-issuing the ALTER TABLE.
A telco company recently came to us looking for an improvement to their Galera deployment. Their two main complaints were the unplanned downtime forced by Galera Cluster [aka MariaDB Cluster or Percona XtraDB Cluster], and the lack of reliable geo-scale deployment.
Continuent showed them how our solution, Tungsten Clustering, provides maximum MySQL uptime and is built for geo-scale (active/passive and active/active) MySQL deployments.
This case study 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.
This case study blog discusses a Telco provider that specializes in roaming, i.e. complete connectivity solutions around the world. It is our third ‘multi-primary MySQL’ blog in our Continuent MySQL Case Study series.
This blog post covers global MySQL / MariaDB / Percona Server clustering with Active/Active meshed replication, the architecture commonly used for globally-distributed SaaS companies.
