Asynchronous Replication Without Censorship
summary
A Percona Server developer and Mail.Ru Target engineer analyzes MySQL replication: explains its internal design, points out flawed choices made in MySQL replication, and examines architectural issues and the multithreaded replication introduced in MySQL 5.7. The talk compares these failures to how PostgreSQL avoided them and argues how replication should have been implemented correctly.
AI-written summary · about
chapters (15)
- 0:00Introduction to async replication
- 1:17Using Lip library
- 2:45How transactions work
- 4:10Replication logs and types
- 9:13Tables as multisets
- 10:39Physical vs logical replication
- 13:08Replication problem diagnosis
- 14:11Replication impact on master
- 15:36Replication parallelism
- 17:23Scalability challenges
- 19:57MySQL 5.7 parallel replication
- 23:34Replication as binary copy
- 26:08Decalog and logical replication
- 28:57MySQL issues and future fixes
- 29:58Q&A
related talks
22mMySQL Replication: Latest Developments
49mMySQL Replication — Advanced Features
14mThe State of the Art of MySQL Replication
51mReplication latest features: the community sceptic roundup
24mComparing the High Availability of MySQL with Modern Distributed SQL Databases
48mDemystifying MySQL Replication Crash Safety
29mEverything You Ever Wanted to Know About MariaDB Replication but Were Afraid to Ask
32mBest Practice in Design and Implementing MySQL Geographic Distributed, High Availability Solutions