Why pub/sub enables real-time messaging in Redis - Visual Breakdown

Concept Flow - Why pub/sub enables real-time messaging

Publisher sends message

↓

Message sent to channel

↓

Subscribers listening on channel

↓

Subscribers receive message instantly

↓

Subscribers process message in real-time

The publisher sends a message to a channel, which is instantly delivered to all subscribers listening on that channel, enabling real-time communication.

Execution Sample

Redis

PUBLISH news "Hello subscribers!"
SUBSCRIBE news
// Subscriber waits and receives message immediately

A publisher sends a message to the 'news' channel, and subscribers listening on 'news' receive it instantly.

Execution Table

Step	Action	Channel	Message	Subscribers State	Result
1	Subscriber subscribes	news	N/A	Listening on 'news'	Ready to receive messages
2	Publisher publishes message	news	"Hello subscribers!"	Listening on 'news'	Message sent to channel
3	Message delivered	news	"Hello subscribers!"	Received message	Subscriber processes message
4	Subscriber waits for next message	news	N/A	Listening on 'news'	Ready for next message

💡 Execution continues as subscribers keep listening; real-time delivery happens instantly on publish.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
Subscribers State	Not listening	Listening on 'news'	Listening on 'news'	Received message	Listening on 'news'

Key Moments - 2 Insights

Why do subscribers receive messages instantly after publishing?

Because subscribers are actively listening on the channel (see execution_table step 1), the message is delivered immediately when published (step 2 and 3).

What happens if no subscriber is listening when a message is published?

The message is sent to the channel but no one receives it because no subscribers are listening (not shown in table but implied by subscriber state).

Visual Quiz - 3 Questions

Look at the execution_table, what is the subscriber state after step 1?

A Listening on 'news'

B Received message

C Not listening

D Disconnected

💡 Hint

Check the 'Subscribers State' column at step 1 in execution_table.

At which step does the subscriber receive the message?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look for 'Received message' in the 'Subscribers State' column in execution_table.

If the subscriber was not listening, what would happen when the publisher sends a message?

A Message is queued until subscriber listens

B Message is lost, no delivery

C Subscriber receives message anyway

D Publisher waits for subscriber

💡 Hint

Refer to key_moments explanation about no subscribers listening.

Concept Snapshot

Pub/Sub in Redis:
- Publisher sends message to a channel.
- Subscribers listen on channels.
- Messages delivered instantly to all subscribers.
- Enables real-time messaging.
- No message queueing if no subscribers.
- Simple, fast, and efficient communication.

Full Transcript

In Redis Pub/Sub, a publisher sends a message to a named channel. Subscribers who have subscribed to that channel receive the message immediately. This happens because subscribers maintain an active connection listening for messages. When the publisher sends a message, Redis delivers it instantly to all subscribers on that channel. If no subscriber is listening, the message is not stored or queued; it is simply lost. This mechanism enables real-time messaging where messages are pushed instantly to all interested clients without delay.