Using MySQL Cluster for Scalability and High Availability (HA)

Leave your reply


There are many different ways to configure MySQL to improve scalability or high availability (HA), with a lot of overlap between these two concepts. Learn how using MySQL Cluster with Servidor Clouds can be used as a solution to provide scalability, high availability, or both.

Use Case: E-Commerce Website

In the following scenarios, the user runs a large e-commerce website which experiences high traffic spikes during sales, and an annual seasonal traffic increase from October to December. Because the site is high-traffic and mission-critical, the user wants to ensure a high uptime and put some measures into place to protect against data loss in case of a server issue.

Scenario 1: Sales and Seasonal Traffic

MySQL Cluster is designed to make it easy to add new servers to the cluster as needed. The user is able to add extra servers ahead of planned sales, and every year before the seasonal traffic begins to increase in October. Servers can be cloned in the Cloud Panel with a few clicks, and brought online within minutes.

After traffic drops, the additional servers can be removed from the cluster as needed, to reduce unnecessary overhead costs.

Scenario 2: Data Redundancy

Because the MySQL data is replicated across multiple servers with MySQL Cluster, the setup automatically provides data redundancy. If one server in the cluster fails, the cluster continues to function without a problem. And thanks to the synchronous data replication, no data is lost in the failure.

Scenario 3: Planned Maintenance

Servers in a MySQL Cluster can be taken offline for maintenance without causing problems for the health of the overall cluster. If necessary, a new server can be added to the cluster before removing an existing server, to ensure that processing power and response time remains steady while the existing server is undergoing maintenance.