Why Pub/sub limitations (no persistence) in Redis? - Purpose & Use Cases

The Big Idea

What if your important message disappears the moment you say it and no one hears it?

The Scenario

Imagine you run a busy coffee shop and shout out orders to your baristas. If a barista isn't in the shop when you call out an order, they miss it completely.

The Problem

Manually shouting orders means if someone isn't listening right then, they lose the message forever. This causes missed orders and unhappy customers.

The Solution

Pub/sub messaging lets you broadcast messages instantly, but without saving them. This means only active listeners get the message, avoiding clutter but risking missed info.

Before vs After

✗ Before

shout('Order 5 is ready!') // if barista not here, they miss it

✓ After

PUBLISH orders 'Order 5 is ready!' // only subscribers listening now get it

What It Enables

Pub/sub enables real-time communication but requires all listeners to be present to catch messages.

Real Life Example

A live chat app where users see messages only if they are online at the moment the message is sent.

Key Takeaways

Pub/sub sends messages instantly to active listeners only.

Messages are not saved, so late listeners miss them.

This is great for live updates but not for guaranteed delivery.

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