Understanding MySQL Master‑Slave Replication: Principles and Benefits

MySQL Master‑Slave Replication

MySQL master‑slave replication is a common high‑availability and data‑architecture solution that synchronizes changes from the master database to one or more slave databases, providing data redundancy, load balancing, and disaster recovery.

Key Features

Real‑time disaster backup for easy failover.

Read‑write separation to reduce master load and improve read performance.

Data backup without impacting business operations.

How It Works

The replication relies on the binary log (binlog). The master records all data changes in the binlog, and the slave reads and replays these events to stay synchronized.

Three Main Steps

1. Master records binlog

When the master executes write operations such as INSERT, UPDATE, or DELETE, it writes the changes to the binlog in addition to the data files. The binlog records the operations, not the data itself, and is flushed to disk after transaction commit.

2. Slave I/O thread pulls the binlog and writes to relay log

After replication starts, the slave’s I/O thread connects to the master, which starts a Binlog Dump thread to send the binlog contents. The slave writes the received events into a local relay log.

3. Slave SQL thread replays the relay log

The slave’s SQL thread reads the relay log and executes the SQL statements in order, bringing the slave data into the same state as the master.