This blog explores the best practices for deploying Tungsten Clustering for MySQL across Availability Zones, outlining the approaches for best high availability, fast response times, and load balancing recommendations.
The Tungsten Connector is an intelligent MySQL proxy that provides key high-availability and read-scaling features. This includes the ability to route MySQL queries by inspecting them in-flight.
Make It Smarter: Tuning MySQL Client Request Routing for Tungsten Connector
Continuent is pleased to announce that Tungsten Clustering 6.1.1 and Tungsten Replicator 6.1.1 are now available! Our 6.1.1 release contains both significant improvements and fixes a number of bugs which improve stability in certain parts of the products.
Continuent is pleased to announce that Tungsten Clustering 5.4.1 and Tungsten Replicator 5.4.1 are now available! Our 5.4.1 release contains both significant improvements and fixes a number of bugs which improve stability in certain parts of the products.
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.
Part of the power of Tungsten Clustering for MySQL / MariaDB is the ability to perform true zero-downtime maintenance, allowing client applications full access to the database layer, while taking out individual nodes for maintenance and upgrades. In this blog post we cover various types of maintenance scenarios, the best practices associated with each type of action, and the key steps to ensure the highest availability.
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.
Continuent is pleased to announce Tungsten Clustering 5.4.0 and Tungsten Replicator 5.4.0 for MySQL / MariaDB. It's significant in that it introduces MySQL 8 support, along with many new features, stability improvements and bug fixes.
Continuent is pleased to announce Tungsten Clustering 6.1.0 and Tungsten Replicator 6.1.0 for MySQL / MariaDB. It's significant in that it has MySQL 8 support, along with many new features, stability improvements and bug fixes. This release also features a new manager, and it also has the ability to do active/active Composite Multimaster geo-clustering.
How to move the Relay role to another node in a Composite Tungsten Cluster
