Comparing the High Availability of MySQL with Modern Distributed SQL Databases
summary
Walks through MySQL HA varieties — native async (master‑slave), semi‑sync, Galera/Percona clusters and InnoDB Group Replication — and calls out concrete limits: single‑writer defaults, full‑copy nodes, manual provisioning, poor handling of large DDLs and cross‑region distribution. Contrasts that with a distributed SQL implementation that uses a two‑layer design, Postgres‑compatible API, Raft consensus, automatic sharding and 3x replication per tablet, enabling zero‑downtime upgrades, automatic resharding and horizontal scale to hundreds of nodes and terabytes.
AI-written summary · about
chapters (6)
- 0:00MySQL and distributed SQL
- 6:14MySQL HA architectures
- 12:17Distributed SQL explained
- 17:41Scalability and multi-master
- 20:31Operational overhead and failover
- 22:00YugabyteDB models and closing
related talks
35mMySQL HA, Recovery and Load Balancing
32mBest Practice in Design and Implementing MySQL Geographic Distributed, High Availability Solutions
52mBest Practices for MySQL High Availability in 2022
27mDistributed MySQL Architectures: Past, Present and Future
54mThe Evolution of a MySQL Database, From a Single Instance to HA With Disaster Recovery
14mThe State of the Art of MySQL Replication
58mDatabase High Availability
49mMySQL Replication — Advanced Features
