Why Master-replica architecture in Redis? - Purpose & Use Cases

The Big Idea

What if your database could handle millions of users without breaking a sweat?

The Scenario

Imagine you run a busy online store. You keep all your product info and orders in one place. When many customers visit at once, your single database gets overwhelmed and slows down. If it crashes, your whole store stops working.

The Problem

Trying to handle all requests with one database is like having one cashier for a huge crowd. It causes long waits and mistakes. Also, if that one database breaks, you lose all your data and customers can't buy anything.

The Solution

Master-replica architecture splits the work. The master handles writing data, while replicas copy the data and handle reading. This way, many customers can get info fast without waiting, and if one replica fails, others keep working smoothly.

Before vs After

✗ Before

SET product:123 "Red Shirt"
GET product:123

✓ After

MASTER: SET product:123 "Red Shirt"
REPLICA: GET product:123

What It Enables

This setup lets your database serve many users quickly and stay reliable even if parts fail.

Real Life Example

A popular social media app uses master-replica to let millions read posts instantly while safely saving new posts without delay.

Key Takeaways

One database alone can slow down and fail under heavy use.

Master-replica splits reading and writing to improve speed and safety.

This architecture keeps apps fast and reliable for many users.

Practice

1. What is the main purpose of the master-replica architecture in Redis?

easy

A. To copy data from one main server to others for safety and speed

B. To delete data from all servers simultaneously

C. To run multiple unrelated databases on one server

D. To encrypt data on the master server only

Solution

1. Step 1: Understand the role of master and replicas

   The master server holds the original data, and replicas copy this data to keep backups and improve read speed.

2. Step 2: Identify the main goal of this setup

   This setup is mainly for safety (backup) and speed (load distribution).

3. Final Answer:

   To copy data from one main server to others for safety and speed -> Option A

4. Quick Check:

   Master-replica = data copy for safety and speed [OK]

Hint: Master copies data to replicas for safety and speed [OK]

Common Mistakes:

• Thinking replicas delete data
• Confusing master-replica with encryption
• Believing replicas run unrelated databases

2. Which Redis command correctly sets a server as a replica of another?

easy

A. REPLICAOF <port>

B. SETREPLICA <port>

C. SLAVEOF <port>

D. COPYTO <port>

Solution

1. Step 1: Recall the Redis command for setting a replica

   The correct command is SLAVEOF followed by the master's IP and port.

2. Step 2: Check the options for exact command syntax

   Only SLAVEOF <port> uses the correct command SLAVEOF.

3. Final Answer:

   SLAVEOF <master-ip> <port> -> Option C

4. Quick Check:

   Set replica with SLAVEOF command [OK]

Hint: Use SLAVEOF to set replica, not REPLICAOF or others [OK]

Common Mistakes:

• Using REPLICAOF instead of SLAVEOF
• Trying non-existent commands like SETREPLICA
• Confusing COPYTO with replication commands

3. Given this Redis command sequence on a replica server:

SLAVEOF 192.168.1.10 6379
GET user:100

What will happen if the master at 192.168.1.10 is down?

medium

A. The replica will return an error because it can't reach the master

B. The replica will return the last synced value for user:100

C. The replica will become master automatically

D. The replica will delete the user:100 key

Solution

1. Step 1: Understand replica behavior when master is down

   The replica keeps the last synced data even if the master is offline.

2. Step 2: Predict the GET command result on replica

   GET will return the last known value for the key from the replica's local data.

3. Final Answer:

   The replica will return the last synced value for user:100 -> Option B

4. Quick Check:

   Replica serves last synced data if master is down [OK]

Hint: Replica serves cached data if master is unreachable [OK]

Common Mistakes:

• Assuming replica errors out when master is down
• Thinking replica auto-promotes to master
• Believing replica deletes keys on master failure

4. You run SLAVEOF NO ONE on a Redis replica server but it still behaves like a replica. What is the likely problem?

medium

A. The server is still connected to the master and did not switch roles

B. The server needs a restart to apply the change

C. The command was typed incorrectly; it should be SLAVE OF NO ONE

D. SLAVEOF NO ONE only works on master servers

Solution

1. Step 1: Understand what SLAVEOF NO ONE does

   This command tells the server to stop replicating and become a master.

2. Step 2: Identify why the server still acts as replica

   If the server is still connected or replication not stopped properly, it remains a replica.

3. Final Answer:

   The server is still connected to the master and did not switch roles -> Option A

4. Quick Check:

   Server must disconnect from master to become master [OK]

Hint: Ensure replica disconnects from master to become master [OK]

Common Mistakes:

• Typing SLAVE OF instead of SLAVEOF
• Thinking restart is always needed
• Believing SLAVEOF NO ONE only works on masters

5. You want to ensure your Redis setup continues working if the master fails. Which approach best uses master-replica architecture?

hard

A. Use only one replica and manually copy data to it daily

B. Disable replication and rely on backups only

C. Run multiple masters without replicas to balance load

D. Set multiple replicas and configure automatic failover to promote a replica to master

Solution

1. Step 1: Identify the goal of continuous operation

   To keep Redis working if master fails, replicas must be ready to take over automatically.

2. Step 2: Evaluate options for failover and replication

   Set multiple replicas and configure automatic failover to promote a replica to master uses multiple replicas and automatic failover, which is the best practice.

3. Final Answer:

   Set multiple replicas and configure automatic failover to promote a replica to master -> Option D

4. Quick Check:

   Multiple replicas + auto failover = high availability [OK]

Hint: Use multiple replicas with auto failover for master failure [OK]

Common Mistakes:

• Relying on manual data copy only
• Running multiple masters without replicas
• Disabling replication and trusting backups alone