Analysis and comparison of five MySQL database reliability solutions this article mainly analyzes and compares five MySQL reliability solutions in terms of basic conditions, costs, advantages and disadvantages, and application scenarios. In addition, this article provides some reference for MySQL database development and management. For details, refer to the following:
1. MySQL Clustering (ndb-cluster stogare)
Introduction:
The high-reliability solution provided by MySQL in the form of storage engines is transaction-safe, real-time data replication, and can be used in scenarios requiring high reliability and load balancing. This solution requires at least three node servers to achieve better results.
Cost:
The node server has a large demand for RAM and is linearly proportional to the database size;
It is best to use a Gigabit Ethernet network;
You also need to use the expensive SCI cards provided by doldolphin.
Advantages:
It can be used in server load balancer scenarios;
It can be used in scenarios with high reliability;
High Scalability;
Real database redundancy;
Easy to maintain.
Disadvantages:
As the database grows, the demand for RAM becomes greater, so the cost is high;
Speed:
It is almost 10 times slower than a typical single server (no Gigabit Ethernet, no SCI card, and storage engine restrictions.
Application scenarios:
Redundancy, high reliability, and load balancing
2. MySQL/GFS-GNBD/HA (Active/Passive)
Introduction:
If multiple MySQL servers use a shared hard disk as data storage, what is the solution?