Replication strategies in DBMS Theory - Step-by-Step Execution

Concept Flow - Replication strategies

Start: Data changes on Primary

↓

Choose Replication Type

↓

Master-Slave

↓

Data copied

↓

Slaves updated

↓

Clients read/write

↓

End

Data changes start at a primary source, then replication type decides how data copies and syncs across nodes, ending with clients accessing updated data.

Execution Sample

DBMS Theory

Primary node receives update
Replication type chosen: Master-Slave
Data copied to Slave nodes
Slaves updated, clients read from Slaves

Shows how data flows from primary to slaves in a Master-Slave replication setup.

Analysis Table

Step	Action	Replication Type	Data State	Result
1	Data updated on Primary	All	Primary has new data	Ready to replicate
2	Replication type chosen	Master-Slave	Primary data unchanged	Prepare to copy to Slaves
3	Data copied to Slaves	Master-Slave	Slaves receive data copy	Slaves data updated
4	Clients read data	Master-Slave	Clients read from Slaves	Clients see updated data
5	Data updated on Primary	Master-Master	Primary node 1 updated	Ready to sync with node 2
6	Data synced between Masters	Master-Master	Both nodes have updated data	Data consistent on both
7	Clients read/write	Master-Master	Clients can write/read on both	High availability
8	Data updated on any node	Multi-Master	Any node updated	Changes propagate to all nodes
9	All nodes synced	Multi-Master	All nodes consistent	Clients read/write anywhere
10	End	All	Replication complete	System consistent
11	Stop	All	No new updates	Replication idle

💡 No new data updates, replication process waits for next change

State Tracker

Variable	Start	After Step 3	After Step 6	After Step 9	Final
Primary Data	Old data	New data updated	New data updated	New data updated	New data updated
Slave Data	Old data	New data copied	N/A	N/A	New data copied
Master 2 Data	Old data	N/A	Synced with Master 1	Synced with all	Synced with all
All Nodes Data	Old data	N/A	N/A	All nodes synced	All nodes synced

Key Insights - 3 Insights

Why does Master-Slave replication only update slaves after primary changes?

Because in Master-Slave, only the primary node accepts writes; slaves get updated copies afterward as shown in execution_table rows 1-4.

How does Master-Master replication keep data consistent on both nodes?

By syncing data changes between both masters after updates, as seen in execution_table rows 5-7, ensuring both have the latest data.

What makes Multi-Master replication different in handling updates?

Any node can accept writes and changes propagate to all nodes, shown in execution_table rows 8-9, allowing flexible read/write access.

Visual Quiz - 3 Questions

Look at the execution_table, at which step do slaves receive updated data in Master-Slave replication?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Check the 'Data copied to Slaves' action in execution_table row 3

According to variable_tracker, after which step are all nodes synced in Multi-Master replication?

A After Step 9

B After Step 3

C After Step 6

D After Step 2

💡 Hint

Look at 'All Nodes Data' row and see when it shows 'All nodes synced'

If data updates only happen on one node, which replication strategy allows clients to write on multiple nodes?

A Master-Slave

B Master-Master

C Multi-Master

D None

💡 Hint

Refer to key_moments about Multi-Master allowing writes on any node

Concept Snapshot

Replication strategies:
- Master-Slave: One primary writes, slaves copy data.
- Master-Master: Two nodes sync data, both can write.
- Multi-Master: Multiple nodes sync, all can write.
Choose based on availability and consistency needs.

Full Transcript

Replication strategies manage how data copies and sync across database nodes. Master-Slave replication has one primary node that accepts writes and copies data to slave nodes for reading. Master-Master replication involves two nodes that both accept writes and keep data synchronized. Multi-Master replication allows multiple nodes to accept writes and sync changes to all nodes. The execution flow starts with data changes on the primary node, then replication type determines how data is copied or synced, and ends with clients accessing updated data. Variables like data on primary, slaves, and other masters change step-by-step as replication proceeds. Key moments include understanding why slaves update after primary in Master-Slave, how Master-Master keeps data consistent, and how Multi-Master allows flexible writes. Visual quizzes test understanding of when slaves update, when all nodes sync, and which strategy allows multi-node writes.

Practice

1. Which replication strategy involves one main server handling all writes and one or more servers copying data from it?

easy

A. Master-Slave replication

B. Master-Master replication

C. Peer-to-Peer replication

D. Snapshot replication

Solution

1. Step 1: Understand Master-Slave replication

   In this strategy, one server (master) handles all write operations, and other servers (slaves) copy data from it.

2. Step 2: Compare with other strategies

   Master-Master allows multiple masters; Peer-to-Peer is decentralized; Snapshot copies data at intervals.

3. Final Answer:

   Master-Slave replication -> Option A

4. Quick Check:

   One main write server = Master-Slave [OK]

Hint: Master-Slave means one master writes, slaves copy [OK]

Common Mistakes:

• Confusing Master-Slave with Master-Master
• Thinking slaves can write data
• Mixing snapshot with continuous replication

2. Which of the following is the correct syntax to describe Master-Master replication?

easy

A. Two servers both accept writes and replicate changes to each other

B. One server writes, others read only

C. Data is copied only once at setup

D. Servers do not communicate

Solution

1. Step 1: Define Master-Master replication

   Both servers can accept writes and replicate changes to each other to keep data synchronized.

2. Step 2: Eliminate incorrect options

   Data is copied only once at setup describes snapshot; One server writes, others read only describes Master-Slave; Servers do not communicate is not replication.

3. Final Answer:

   Two servers both accept writes and replicate changes to each other -> Option A

4. Quick Check:

   Master-Master means both write and sync [OK]

Hint: Master-Master means both servers write and sync [OK]

Common Mistakes:

• Thinking only one server writes in Master-Master
• Confusing snapshot with replication
• Assuming no communication means replication

3. Consider a Master-Slave replication setup where the master server receives 100 write requests per second. If slaves replicate with a delay of 2 seconds, what is the expected delay in data consistency on slaves?

medium

A. Immediate consistency

B. No delay, slaves write directly

C. 2 seconds delay

D. 100 seconds delay

Solution

1. Step 1: Understand replication delay

   Slaves replicate data from master with a 2-second delay, so data on slaves lags behind master by 2 seconds.

2. Step 2: Analyze options

   Immediate consistency means no delay, which is incorrect. 100 seconds delay is unrelated to request rate. Slaves do not write directly.

3. Final Answer:

   2 seconds delay -> Option C

4. Quick Check:

   Replication delay = 2 seconds [OK]

Hint: Replication delay equals slave lag time [OK]

Common Mistakes:

• Confusing request rate with delay time
• Assuming slaves write directly
• Thinking slaves are always immediately consistent

4. A database administrator sets up Master-Master replication but notices data conflicts when both servers write the same record simultaneously. What is the best way to fix this?

medium

A. Allow only one server to write at a time without syncing

B. Switch to Master-Slave replication

C. Disable replication entirely

D. Implement conflict resolution rules or use timestamps

Solution

1. Step 1: Identify cause of conflicts

   Simultaneous writes cause conflicts in Master-Master replication because both servers can change the same data.

2. Step 2: Apply conflict resolution

   Using rules like timestamps or last-write-wins helps resolve conflicts automatically.

3. Final Answer:

   Implement conflict resolution rules or use timestamps -> Option D

4. Quick Check:

   Conflict resolution fixes simultaneous writes [OK]

Hint: Use conflict rules to fix Master-Master write clashes [OK]

Common Mistakes:

• Thinking disabling replication solves conflicts
• Switching to Master-Slave without need
• Ignoring conflict resolution mechanisms

5. You want a replication strategy that provides high availability and allows writes on multiple servers but can tolerate occasional conflicts. Which strategy fits best?

hard

A. Master-Slave replication

B. Master-Master replication

C. Snapshot replication

D. No replication

Solution

1. Step 1: Analyze requirements

   High availability and multiple write servers require a strategy where more than one server can accept writes.

2. Step 2: Match strategy to needs

   Master-Master replication allows multiple write servers but may have conflicts; Master-Slave does not allow multiple writes.

3. Final Answer:

   Master-Master replication -> Option B

4. Quick Check:

   Multiple writes + availability = Master-Master [OK]

Hint: Multiple write servers need Master-Master replication [OK]

Common Mistakes:

• Choosing Master-Slave for multiple writes
• Ignoring conflict tolerance
• Thinking snapshot replication supports writes