MySQL Cluster high-availability architecture

Objective

High-availability architectures are basically standard for Internet services, and are highly available both for application services and for database services. For a system, it may contain many modules, such as front-end application, cache, database, search, message queue, etc., each module needs to be highly available to ensure the high availability of the whole system. For database services, high availability may be more complex, the user's services available, not only access, but also need to have correctness assurance, so the high availability of the database is always a hot topic, today on a variety of high-availability programs, talk about personal views, if there are errors, please correct me!!

MySQL Master-Slave architecture

This kind of architecture, general start-up enterprises are more commonly used, but also facilitate the expansion of the back step

This architecture features:

1. Low cost, rapid and convenient deployment

2. Read/write separation

3, can also reduce the reading pressure by adding the library in time

4, the main library single point of failure

5, data consistency problem (synchronization delay caused)

Mysql+drdb Architecture

By using the copy mode of block block based on DRBD, the two-master failover is solved to a large extent to solve the problem of single point failure of Main library.

This architecture features:

1, high-availability software can use heartbeat, fully responsible for VIP, data and the management of DRBD services

2, the main fault can automatically switch quickly, and from the library can still be through the VIP and the new master library for data synchronization

3, from the library also supports read and write separation, can use middleware or program implementation

Mysql+mha Architecture

MHA is now a relatively mature and common solution in MySQL's high-availability scenario, developed by the Japanese, that MHA can quickly and automatically switch operations during MySQL failover, while maintaining data consistency to the maximum

This architecture features:

1, installation of the deployment of simple, without affecting the existing structure

2. Automatic monitoring and failover

3. Ensure data consistency

4, failover mode can use manual or automatic multi-directional selection

5. Large adaptation range (for any storage engine)

mysql+mmm Architecture

MMM is the Master-master Replication Manager for MySQL (MySQL master replication Manager), which is about the monitoring of the MySQL primary master replication configuration, A set of scalable script packages for failover and management (at any time only one node can be written), this suite can also be based on a standard master-slave configuration of any number of read load balancing from the server, so you can use it in a group of replicated servers to start the virtual IP, in addition, it has to implement data backup , and a script that synchronizes the functionality between nodes.
MySQL itself does not provide replication failover solution, through the MMM solution can realize the server failover, so as to achieve high availability of MySQL.

This scheme features:

1, security, high stability, scalability is good

2, the number of servers required at least three or more

3, to the dual-master (high-master replication requirements)

4, can also achieve read and write separation

MySQL Cluster Architecture

MySQL official launch of the cluster high-availability program, because I have not used, bad evaluation

Excerpt from an explanation on the web

MySQL Cluster is made up of a group of computers, each running a variety of processes, including MySQL servers, NDB Cluster data nodes, Management servers, and (possibly) specialized data access programs.
Due to the complexity of the MySQL Cluster architecture, the deployment time (which usually takes a few hours for the DBA to complete), and the MySQL Cluster Manager requires only one command to complete, but MySQL Cluster manager is charged. And industry insiders believe that NDB is not suitable for most business scenarios and has security concerns. As a result, fewer people are being used.

MySQL Cluster high-availability architecture