Pub/sub limitations (no persistence) in Redis - Mini Project: Build & Apply

Understanding Redis Pub/Sub Limitations: No Persistence

📖 Scenario: You are building a simple chat application using Redis Pub/Sub. You want to understand how messages are delivered and what happens if a user is offline.

🎯 Goal: Create a Redis Pub/Sub setup that demonstrates message publishing and subscribing, and observe the limitation that messages are not stored if the subscriber is offline.

📋 What You'll Learn

Create a Redis channel named chatroom

Subscribe to the chatroom channel

Publish messages to the chatroom channel

Demonstrate that messages sent while subscriber is offline are not received

💡 Why This Matters

🌍 Real World

Many chat apps and real-time systems use Redis Pub/Sub for instant messaging but must handle the limitation that messages are not saved if users are offline.

💼 Career

Understanding Redis Pub/Sub limitations is important for backend developers and system architects designing real-time communication systems.

1

Create a Redis channel named chatroom

Write the Redis command to create a channel named chatroom by subscribing to it using the command SUBSCRIBE chatroom.

Redis

# Use the command to subscribe to the chatroom channel
# Your code here

Hint

Use the SUBSCRIBE command followed by the channel name chatroom.

2

Publish a message to the chatroom channel

Write the Redis command to publish the message Hello everyone! to the chatroom channel using PUBLISH chatroom "Hello everyone!".

Redis

SUBSCRIBE chatroom
# Publish a message to the chatroom channel
# Your code here

Hint

Use the PUBLISH command with the channel name and the message in quotes.

3

Simulate subscriber offline and publish a message

Write the Redis command to publish the message Are you there? to the chatroom channel while no subscriber is connected, using PUBLISH chatroom "Are you there?".

Redis

SUBSCRIBE chatroom
PUBLISH chatroom "Hello everyone!"
# Publish a message while subscriber is offline
# Your code here

Hint

Use the PUBLISH command again with the new message.

4

Explain the limitation of Redis Pub/Sub with no persistence

Add a comment explaining that Redis Pub/Sub does not store messages, so if a subscriber is offline, it will miss messages published during that time.

Redis

SUBSCRIBE chatroom
PUBLISH chatroom "Hello everyone!"
PUBLISH chatroom "Are you there?"
# Your explanation here

Hint

Write a comment starting with # explaining the no persistence limitation.

Practice

1. What happens to messages sent via Redis Pub/sub if no clients are subscribed at that moment?

easy

A. Messages are lost and not stored anywhere.

B. Messages are saved and delivered later when clients subscribe.

C. Messages are queued until a client connects.

D. Messages are stored in a Redis list automatically.

Solution

1. Step 1: Understand Redis Pub/sub behavior

   Redis Pub/sub delivers messages only to clients currently subscribed.

2. Step 2: Analyze message persistence

   Since Pub/sub does not save messages, if no client listens, messages are lost.

3. Final Answer:

   Messages are lost and not stored anywhere. -> Option A

4. Quick Check:

   Pub/sub = no persistence [OK]

Hint: Pub/sub delivers live only, no message storage [OK]

Common Mistakes:

• Assuming messages queue up for later delivery
• Thinking messages are saved automatically
• Confusing Pub/sub with Redis streams

2. Which of the following is the correct Redis command to subscribe to a channel named news?

easy

A. SUBSCRIBE TO news

B. PUBLISH news

C. SUBSCRIBE news

D. LISTEN news

Solution

1. Step 1: Recall Redis Pub/sub subscribe syntax

   The correct command to subscribe is SUBSCRIBE <channel>.

2. Step 2: Match command to channel name

   Using SUBSCRIBE news subscribes to the channel named 'news'.

3. Final Answer:

   SUBSCRIBE news -> Option C

4. Quick Check:

   Subscribe syntax = SUBSCRIBE channel [OK]

Hint: Subscribe uses 'SUBSCRIBE channel' command [OK]

Common Mistakes:

• Using PUBLISH instead of SUBSCRIBE
• Adding extra words like TO
• Using LISTEN which is not a Redis command

3. Consider this Redis Pub/sub scenario:

Client A subscribes to channel 'chat'.
Client B publishes message 'Hello' to 'chat'.
Client C subscribes to 'chat' after the message is published.

Which clients receive the message 'Hello'?

medium

A. Only Client A

B. Clients A and C

C. Only Client C

D. Clients A, B, and C

Solution

1. Step 1: Identify subscribers at publish time

   Only Client A was subscribed when Client B published the message.

2. Step 2: Understand Pub/sub delivery

   Messages are sent only to clients subscribed at publish time; Client C subscribed later and misses the message.

3. Final Answer:

   Only Client A -> Option A

4. Quick Check:

   Subscribers at publish = receivers [OK]

Hint: Only current subscribers get messages [OK]

Common Mistakes:

• Assuming late subscribers get past messages
• Including publisher as receiver
• Thinking all clients get all messages

4. You wrote this Redis Pub/sub code snippet:

SUBSCRIBE news
PUBLISH news "Update 1"

But your subscriber never receives the message. What is the likely problem?

medium

A. The PUBLISH command syntax is incorrect.

B. The subscriber must be subscribed before the message is published.

C. Redis does not support Pub/sub messaging.

D. The channel name 'news' is reserved and cannot be used.

Solution

1. Step 1: Check Pub/sub message delivery timing

   Subscribers must be listening before messages are published to receive them.

2. Step 2: Analyze the code order

   If PUBLISH runs before SUBSCRIBE completes, subscriber misses the message.

3. Final Answer:

   The subscriber must be subscribed before the message is published. -> Option B

4. Quick Check:

   Subscribe first, then publish [OK]

Hint: Subscribe before publish to receive messages [OK]

Common Mistakes:

• Thinking PUBLISH syntax is wrong
• Believing Redis lacks Pub/sub support
• Assuming channel names are restricted

5. You want to ensure messages are not lost if no clients are currently subscribed. Which Redis feature should you use instead of Pub/sub?

hard

A. Use Redis transactions to save messages.

B. Use Pub/sub with multiple channels.

C. Increase Redis memory to save messages.

D. Redis Streams to store and consume messages later.

Solution

1. Step 1: Understand Pub/sub limitation

   Pub/sub does not store messages; they are lost if no subscriber is present.

2. Step 2: Identify Redis feature for persistence

   Redis Streams allow storing messages so clients can read them later.

3. Step 3: Evaluate other options

   Using multiple channels or transactions does not provide message persistence; increasing memory does not save messages automatically.

4. Final Answer:

   Redis Streams to store and consume messages later. -> Option D

5. Quick Check:

   Use Streams for persistence, not Pub/sub [OK]

Hint: Use Redis Streams for message persistence [OK]

Common Mistakes:

• Trying to fix Pub/sub by adding channels
• Thinking transactions save Pub/sub messages
• Assuming more memory stores messages