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.
The power of Tungsten Clustering for MySQL / MariaDB is its built-in intelligent MySQL proxy, known as the Tungsten Connector. The Connector has built-in read-write splitting capabilities, and it is also possible to configure different algorithms which select the appropriate slave (i.e. Round-Robin or Lowest-Latency).
The replicator is a critical piece of the Tungsten Clustering solution for MySQL / MariaDB, as well as its own stand-alone data replication product. Automatic recovery enables the replicator to go back online in the event of a transient failure. In this blog, we discuss how to enable Autorecovery.
Every time I use awk, my respect for it grows! Like grep, find and rsync, it is one of the powerhouse command-line tools in my arsenal. Recently, I needed to list all MySQL binary log files from a starting file forwards in sequence. AWK to the rescue! For example, I knew the starting file was […]
erics, August 29th, 2019 
Categories: Connector, Geo-Distributed, Maintenance, Multimaster, Multimaster MySQL, Multisite AWS, Clustering, Disaster REcovery, High Availability, mysql, proxy, Replicator
| 
Comments Off on 10 Reasons Why Tungsten Clustering Beats the DIY Approach for Geo-Distributed MySQL Deployments 
