MySQL master-slave synchronization outage Switching problem

1) MySQL versions have been optimized for master-slave synchronization

2) 5.7 is loss less, but not zero loss, when switching the data will be lost

3) 5.7 True concurrent replication reduces master-slave delay, 5.6 No (based on the schema level)

4) PG has a full synchronous replication mode, MySQL native version is not (only semi-synchronous). The Galera,phxsql,alisql solves the problem of switching data loss and master-slave delay.

5) Even if the master-slave delay is not accepted (such as money-related business) in the event of a switchover under a special business (financial), this scenario must be fully synchronized such as with Galera,phxsql,alisql. For a large amount of business can only build a cluster of horizontal split solution

MySQL master-slave synchronization outage Switching problem