Asynchronous Replication Without Censorship
summary
A Percona Server developer and Mail.Ru Target engineer examines MySQL’s asynchronous replication, identifies why past design choices failed, and explains MySQL’s replication architecture including the multithreaded replication introduced in MySQL 5.7. The talk analyzes architectural problems in MySQL replication, contrasts how replication should have been implemented, and why PostgreSQL avoided those issues.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 1:17Purpose of replication
- 3:05Data integrity in databases
- 5:38Storage engine and replication
- 7:22Replication logs types
- 9:13Relational tables issues
- 10:59Physical vs logical replication
- 12:47Diagnosing replication lag
- 14:11Replication challenges
- 15:56Parallel replication limits
- 17:23Replication scalability
- 19:13MySQL 5.7 parallel replication
- 20:18Replication types summary
- 22:02Master impact on replication
- 23:31Replica for reporting
- 24:36Schema changes and replication
- 25:39Logical replication flexibility
- 26:42Decoding and streaming replication
- 28:09Ideal replication journal
- 28:54MySQL replication limits
- 29:17Key takeaways
- 30:19When to use replication
- 33:09Upgrading MySQL
- 34:11Alternative engines
- 35:59Why MySQL replication
- 37:24Hardware details
- 38:28CPU utilization
- 39:34MariaDB vs MySQL improvements
related talks
22mMySQL Replication: Latest Developments
14mThe State of the Art of MySQL Replication
49mMySQL Replication — Advanced Features
24mComparing the High Availability of MySQL with Modern Distributed SQL Databases
51mReplication latest features: the community sceptic roundup
21mHow Safe is Asynchronous Master-Master Setup?
31m#PostgreSQL to #MySQL: A DBA Perspective
27mDistributed MySQL Architectures: Past, Present and Future