Replication for MySQL DBAs
MySQL replication copies changes from a source server to one or more replicas using the binary log, so reads can scale and a standby copy exists. Modern setups use GTIDs to track transactions, and replication can be asynchronous or semi-synchronous.
Stage: High Availability · Part of the MySQL DBA roadmap · Last reviewed 19 November 2026
What to learn in Replication
- Configure a source and replica using GTID based replication
- Check replica health with SHOW REPLICA STATUS and read the lag fields
- Explain statement based, row based and mixed binary logging
- Route reads to a replica while keeping writes on the source
- Promote a replica after a source failure and repoint other replicas
Replication interview questions
What is a GTID in MySQL replication?
A global transaction identifier is a unique ID, made of the source server UUID and a sequence number, attached to each committed transaction. Replicas use it to know exactly which transactions they have applied, which makes failover and repointing much simpler than binlog file positions.
Why can a MySQL replica fall behind the source?
Causes include a single-threaded applier on busy sources, long running transactions, slow disks or network on the replica, and heavy reads on the replica. Multi-threaded replication, better indexes and resizing the replica help reduce lag.
Where Replication fits in the MySQL DBA roadmap
Replication belongs to the High Availability stage (advanced level). Scale and survive.
Other units in this stage
Back to the full MySQL DBA roadmap