Real-time notification pattern in Redis - Step-by-Step Execution

Concept Flow - Real-time notification pattern

Client A publishes message

↓

Redis receives message

↓

Redis broadcasts message to subscribers

↓

Client B receives notification

↓

Client B processes notification

This flow shows how a message published by one client is received by Redis and then broadcast to all subscribed clients in real-time.

Execution Sample

Redis

PUBLISH notifications "New message"
SUBSCRIBE notifications

Client A publishes a message to the 'notifications' channel; Client B subscribes and receives it immediately.

Execution Table

Step	Action	Redis State	Clients State	Output/Result
1	Client B subscribes to 'notifications'	Channel 'notifications' has 1 subscriber (Client B)	Client B waiting for messages	No output yet
2	Client A publishes 'New message' to 'notifications'	Message published to 'notifications' channel	Client B receives 'New message'	Client B outputs notification: 'New message'
3	Client B processes the notification	No change	Client B processed message	Notification handled
4	No more messages	No new messages in channel	Clients idle	Waiting for next publish

💡 No more messages published; clients remain subscribed waiting for new notifications

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
Redis Channel 'notifications' Subscribers	0	1 (Client B)	1 (Client B)	1 (Client B)	1 (Client B)
Published Message for 'notifications'	empty	empty	"New message"	empty	empty
Client B State	disconnected	subscribed, waiting	received message	processed message	waiting

Key Moments - 2 Insights

Why does Client B receive the message immediately after Client A publishes it?

Because Client B is subscribed to the 'notifications' channel before the message is published, as shown in execution_table step 1 and 2.

What happens if Client B subscribes after Client A publishes the message?

Client B will not receive the past message because Redis Pub/Sub only delivers messages to clients subscribed at the time of publishing, as implied by the execution_table.

Visual Quiz - 3 Questions

Look at the execution_table at step 2, what is the Redis state?

A Message published to 'notifications' channel

B Channel 'notifications' has 0 subscribers

C No messages in queue

D Client B disconnected

💡 Hint

Check the 'Redis State' column at step 2 in execution_table

At which step does Client B process the notification?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at the 'Clients State' and 'Output/Result' columns in execution_table

If Client B subscribes after Client A publishes, what changes in the execution_table?

A Client B receives the message immediately

B Client B does not receive the past message

C Message queue holds the message until Client B subscribes

D Redis stores the message permanently

💡 Hint

Refer to key_moments explanation about subscription timing and message delivery

Concept Snapshot

Real-time notification pattern uses Redis Pub/Sub.
Clients subscribe to channels to receive messages.
Publishers send messages to channels.
Redis broadcasts messages instantly to all subscribers.
Subscribers only get messages published after they subscribe.

Full Transcript

The real-time notification pattern in Redis works by clients subscribing to channels. When a client publishes a message to a channel, Redis immediately broadcasts it to all clients subscribed to that channel. The execution flow starts with a client subscribing, then another client publishing a message. Redis broadcasts the message to subscribers. The subscriber receives and processes the message. If a client subscribes after a message is published, it will not receive that past message because Redis Pub/Sub delivers only to current subscribers. This pattern enables instant notifications between clients using Redis channels.

Practice

1. What is the main purpose of the PUBLISH command in Redis real-time notification pattern?

easy

A. To store data permanently

B. To send messages to a specific channel

C. To listen for messages on a channel

D. To delete a channel

Solution

1. Step 1: Understand the role of PUBLISH

   The PUBLISH command is used to send messages to a channel in Redis.

2. Step 2: Differentiate from SUBSCRIBE

   SUBSCRIBE listens for messages, but PUBLISH sends them.

3. Final Answer:

   To send messages to a specific channel -> Option B

4. Quick Check:

   PUBLISH sends messages [OK]

Hint: PUBLISH sends, SUBSCRIBE listens [OK]

Common Mistakes:

• Confusing PUBLISH with SUBSCRIBE
• Thinking PUBLISH stores data
• Assuming PUBLISH deletes channels

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

easy

A. LISTEN news

B. PUBLISH news

C. SUBSCRIBE('news')

D. SUBSCRIBE news

Solution

1. Step 1: Recall Redis SUBSCRIBE syntax

   The correct syntax is SUBSCRIBE channel_name without parentheses.

2. Step 2: Check each option

   SUBSCRIBE news matches the correct syntax. SUBSCRIBE('news') uses parentheses which is invalid in Redis CLI.

3. Final Answer:

   SUBSCRIBE news -> Option D

4. Quick Check:

   SUBSCRIBE channel_name [OK]

Hint: SUBSCRIBE uses plain command and channel name [OK]

Common Mistakes:

• Using parentheses like a function call
• Confusing PUBLISH with SUBSCRIBE
• Using LISTEN which is not a Redis command

3. Consider this Redis command sequence:

SUBSCRIBE updates
PUBLISH updates "New message arrived"

What will the subscriber receive?

medium

A. "New message arrived" on the updates channel

B. No message because SUBSCRIBE blocks commands

C. An error because PUBLISH cannot be used after SUBSCRIBE

D. The message on a different channel

Solution

1. Step 1: Understand SUBSCRIBE behavior

   SUBSCRIBE listens to messages on the specified channel and receives published messages.

2. Step 2: Analyze PUBLISH effect

   PUBLISH sends the message "New message arrived" to the updates channel, which the subscriber listens to.

3. Final Answer:

   "New message arrived" on the updates channel -> Option A

4. Quick Check:

   SUBSCRIBE receives PUBLISH messages [OK]

Hint: SUBSCRIBE gets messages published to its channel [OK]

Common Mistakes:

• Thinking SUBSCRIBE blocks all commands
• Believing PUBLISH causes errors after SUBSCRIBE
• Assuming messages go to wrong channels

4. You wrote this Redis command sequence:

SUBSCRIBE updates
PUBLISH updates "Hello"
UNSUBSCRIBE updates
PUBLISH updates "Bye"

Why does the subscriber not receive the "Bye" message?

medium

A. Because SUBSCRIBE blocks PUBLISH commands

B. Because PUBLISH only works before SUBSCRIBE

C. Because UNSUBSCRIBE stops listening to the channel

D. Because messages are lost after first publish

Solution

1. Step 1: Understand UNSUBSCRIBE effect

   UNSUBSCRIBE removes the subscriber from the channel, so it stops receiving messages.

2. Step 2: Analyze message delivery after UNSUBSCRIBE

   After unsubscribing, the subscriber no longer listens, so "Bye" is not received.

3. Final Answer:

   Because UNSUBSCRIBE stops listening to the channel -> Option C

4. Quick Check:

   UNSUBSCRIBE stops message reception [OK]

Hint: UNSUBSCRIBE stops listening, no more messages [OK]

Common Mistakes:

• Thinking PUBLISH only works before SUBSCRIBE
• Assuming messages are lost after first publish
• Believing SUBSCRIBE blocks PUBLISH commands

5. You want to build a real-time notification system using Redis where multiple users subscribe to different channels. Which approach ensures users only get messages for their subscribed channels without missing any messages?

hard

A. Use PUBLISH/SUBSCRIBE pattern and keep subscribers connected continuously

B. Use Redis lists to push messages and clients poll periodically

C. Use PUBLISH to send messages and clients fetch keys manually

D. Use Redis transactions to lock channels during message send

Solution

1. Step 1: Understand real-time delivery needs

   Real-time notifications require instant delivery without polling delays.

2. Step 2: Evaluate options for message delivery

   PUBLISH/SUBSCRIBE keeps clients connected and delivers messages instantly to subscribed channels.

3. Step 3: Compare with alternatives

   Polling (Use Redis lists to push messages and clients poll periodically) causes delays; fetching keys manually (Use PUBLISH to send messages and clients fetch keys manually) is inefficient; transactions (Use Redis transactions to lock channels during message send) do not help with message delivery.

4. Final Answer:

   Use PUBLISH/SUBSCRIBE pattern and keep subscribers connected continuously -> Option A

5. Quick Check:

   Continuous SUBSCRIBE ensures real-time messages [OK]

Hint: Keep subscribers connected with PUBLISH/SUBSCRIBE [OK]

Common Mistakes:

• Using polling instead of real-time subscription
• Trying to fetch messages manually
• Misusing transactions for message delivery