Analysis and comparison of five MySQL database Reliability Solutions (3) advantages:
High Reliability;
A certain degree of redundancy;
In the name of high reliability, it is scalable.
Disadvantages:
No server load balancer
Unguaranteed redundancy
No scalability in writing load
Speed:
Reading and writing is equivalent to a separate server.
Application scenarios
Highly reliable and read-intensive applications
4. MySQL Write Master/Multiple MySQL Read Slaves (Active/Active)
Introduction:
Consider different read and write database connections. You can use one master server for write operations, and n slave servers for read operations.
Cost:
The cost of up to one high-performance write server and n read servers
Advantages:
High Reliability of read operations;
Load balancing of read operations;
Load balancing for read operations is scalable.
Disadvantages:
High reliability without write operations;
Load balancing without write operations;
No scalability in write operations;
Speed:
Same as a single server; better support for reading operations
Application scenarios
READ-intensive applications that require high reliability and load balancing.
5. Standalone MySQL Servers (Functionally separated) (Active)
Multiple independent servers with separated functions do not have high reliability and load balancing capabilities. they have many obvious disadvantages and are not considered.
Summary:
The HA solution recommended on the official MySQL website is combined with DRBD (solution 3 in this article) and Replication (Solution 4 in this article ). In addition to Linux Heartbeat, we can also implement the Auto-failover function. in this case, we will find that the down time will be greatly reduced.