The database multi-node redundancy design reaches the cluster pxc, which helps prevent the operation of the entire project after a single node failure
The advantage of using the pxc cluster solution is to ensure the strong consistency of the data of each database node in the cluster, but it also needs to consume a lot of performance to achieve this goal. For high-value data such as amount and transaction, it is necessary to ensure consistency.
Generally, haproxy can be used as middleware for database load balancing
Generally, you can use Ali's open source data segmentation middleware mycat
Fortune 500 enterprise architecture:
Since the PXC cluster cannot be installed directly under the window system, the Docker virtual machine can be used to deploy the Mysql cluster
To put it bluntly, the pxc cluster means sub-databases and sub-nodes. The data of each database is synchronized in both directions. Read and write can be performed (write data is slow)
However, the data of the replication cluster is one-way synchronized, which realizes the read-write separation mechanism. One library is used for reading, and the other is used for writing. The synchronization is for reading (it may cause data loss) (write data fast)
master-->slave