[Fun with MySQL Replication] copying a topology

Simple and simple is true. Those high-end foreign copy topologies are purely self-abuse.
There are about four principles for implementing replication:

① A master database can have multiple slave Databases
② One slave database can only have one master database
③ Each slave Database Server ID is globally unique
④ Log_slave_updates has the utility of pass-through

The following is a brief introduction to the Topology Design of several types of replication, their advantages and disadvantages, and their application scenarios, which will be available soon.

(I) one master and one slave

Short Comment: The simplest Topology
Recommendation index:★★★★★



(Ii) one master, multiple slave



Short Comment: every slave database crashes
Recommendation index:★★★★☆



(Iii) Active-active dual-master Replication



Short Comment: Anti-cracking
Recommendation index: ☆☆☆☆☆



(Iv) Active-active dual-master in passive mode



Short Comment: one of the primary databases is read-only, which is a very important and common topology.
Recommendation index:★★★★★



(V) Dual-master replication with slave Databases



Short Comment: increase redundancy and eliminate single point of failure
Recommendation index:★☆☆☆☆☆



(6) Circular Replication


Short Comment: fragile Topology
Recommendation index: ☆☆☆☆☆



(Vii) master database-distribution master database-slave Database


Short Comment: The distribution of the master database is actually a slave database, the only purpose is to extract and provide the binlog of the master database, reduce the burden on the master database
Recommendation index:★★★☆☆



Replicate tree


Short Comment: Let Data fly and let read performance fly
Recommendation index:★★★☆☆