Mysql Architecture Evolution

MySQL small high-availability architecture solution: MySQL dual-master, master-slave + Keepalived master-slave automatic switch server resources: two pcservers advantages: simple architecture, Resource Saving disadvantages: linear expansion is not possible, after a master-slave failure occurs, you must manually restore the master-slave architecture. MySQL medium high-availability architecture solution: MMM + MySQL dual-master + Multi-slave high-availability solution server asset

MySQL small high-availability architecture solution: MySQL dual-master, master-slave + Keepalived master-slave automatic switching Server resources: two PC servers advantages: simple architecture, Resource Saving disadvantages: linear expansion is not possible, after a master-slave failure occurs, you must manually restore the master-slave architecture. MySQL medium high-availability architecture solution: MMM + MySQL dual-master + Multi-slave high-availability solution server asset

MySQL small high-availability architecture
Solution: MySQL dual-master, master-slave, and Keepalived automatic master-slave failover

Server resources: two PC servers
Advantages: simple architecture and Resource Saving
Disadvantage: linear expansion is not possible. You need to manually restore the master-slave architecture after the master-slave architecture fails.

MySQL medium-sized high-availability architecture
Solution: MMM + MySQL dual-master + Multi-slave high availability solution

> Server resources:
1. At least five PC servers, two MySQL master databases, two MySQL slave databases, and one MMM Monitor;
2. Select a low configuration for one MMM Monitor;
3. If F5 is not used as the Load balancer for the slave database, two PC servers can be used to deploy LVS or HAProxy + Keepalived combinations;
Advantages: Dual-master hot standby mode, read/write splitting, and linear expansion of SLAVE Clusters
Disadvantage: read/write splitting needs to be solved on the program side. Master/Slave latency occurs when the Master node writes data in large batches.

MySQL large high-availability architecture
Main Idea: middleware + MySQL Sharding
Such as solutions: middleware and MySQL technologies such as Cobar
Image omitted.
Some mainstream high-availability architectures of MySQL are also shared.

1. MySQL dual-master + Keepalived Master/Slave automatic switchover solution (as shown above)
2. Master-slave MySQL + Keepalived master-slave automatic failover solution (as shown above)
3. MMM + MySQL dual-master + Multi-slave high availability solution (available above)
4. MySQL + Pecemaker (Heartbeat) + DRBD High Availability
5. MySQL + RHCS high availability solution
6. MySQL + Cluser cluster architecture
7. Percona Xtradb Cluster High Availability Solution
8. Middleware + MySQL large cluster solution (as mentioned above)
MySQL + Pecemaker (Heartbeat) + DRBD High Availability & MySQL + RHCS high availability solution

Percona Xtradb Cluster High Availability Solution

MySQL multi-data center deployment architecture reference

Original article address: Mysql Architecture Evolution, thanks to the original author for sharing.