Watch the replay of a webinar with our colleagues from Datavail and hosted by DBTA during which we discuss whether “free” is really good enough for business-critical MySQL database environments.
Real time database replication is a must for clustering and other key business purposes, like reporting. There are a number of replication technologies available for MySQL, and some are even bundled into various solutions. When choosing a replication methodology, it is paramount to understand just how the data moves from source to target. In this blog post, we will examine how asynchronous, synchronous, and "semi-synchronous" replication behave when used for clustering. Also, we will explore how replication affects database performance and data availability.
Read our white paper on Tungsten Clustering for MySQL, MariaDB and Percona Server. Tungsten Clustering allows enterprises running business-critical database applications to cost-effectively achieve continuous operations on a global scale.
In this blog post, we explore the correct way to implement bi-directional Tungsten Replication between AWS Aurora and Tungsten Clustering for MySQL databases.
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.
Database Administration is a tough, often ungrateful job. Especially if you run a 24/7 business-critical MySQL or MariaDB deployment.
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.
Database Proxies provide a single entry point into MySQL for the calling client applications. Proxies are wonderful tools to handle various situations like a master role switch to another node for maintenance, or for transparency with read and write connections. However, when the time comes to perform the switch action, all of the calling clients have been funneled through the proxy, so identification of the calling host from the database itself becomes difficult.
