Enterprise Mysql multi-instance master-slave Replication

1. Problem Background: 2. database architecture diagram: 3. Solution: 4. Solution: 5. Result Test: 1. Problem Background: the company's two mysql servers do not have A master-slave replication architecture. Database a and database B run on server

1. Problem Background: 2. database architecture diagram: 3. Solution: 4. Solution: 5. Result Test: 1. Problem Background: the company's two mysql servers do not have A master-slave replication architecture. Database a and database B run on server

1. Background:

2. database architecture diagram:

3. solution:

4. solution:

5. Test results:

1. Background:

The company's two mysql servers do not have A master-slave replication architecture. Database a and database B run on server A, database d and database e run on server B, and database, server B runs different tables in database c, so both servers A and B actually work in standalone mode, but they do database/table sharding, however, the database security and service continuity cannot be guaranteed.

2. Database Server architecture diagram: server a ip Address: 192.168.3.102, server B IP Address: 192.168.3.100

5. Test results:

Create and delete A database on the instance with port 3306 of the master server A, and then check whether the database of the instance with port 3307 of server B has changed:

This article is from the "Sea sky" blog. Please keep this source