This is the second post in a series of MySQL case study blogs. It discusses a SaaS provider dealing with sensitive medical data and their need to be able to quickly deploy clusters in AWS and recover from multi-zone AWS outages.
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.
How to move the Relay role to another node in a Composite Tungsten Cluster
When it comes to zero downtime, proxies are the first line components of a cluster. In order to achieve High Availability (HA) for MySQL, MariaDB and Percona Server, a commonly deployed setup consists of configuring load balancers (hardware or software) on top of those proxies.
Tungsten Clustering offers a graphical administration tool called the Tungsten Dashboard™ to help with your management burden. The GUI makes the deployment much easier to visualize and administer.
In this blog post, we discuss failover concepts and administration.
The Tungsten Replicator is an extraordinarily powerful and flexible tool capable of moving vast volumes of data from source to target.
The Tungsten Replicator is an extraordinarily powerful and flexible tool capable of moving vast volumes of data from source to target.
In this blog post we will discuss the basics of how to implement and use filters in the Tungsten Replicator.
