Real-time notification pattern in Redis - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the Real-time notification pattern in Redis?

It is a way to send instant messages or alerts to users or systems using Redis features like Pub/Sub or Streams, allowing immediate updates without delay.

beginner

How does Redis Pub/Sub help in real-time notifications?

Redis Pub/Sub lets publishers send messages to channels and subscribers receive them instantly, enabling real-time communication without storing messages.

intermediate

What is a key difference between Redis Pub/Sub and Redis Streams for notifications?

Pub/Sub delivers messages instantly but does not store them; Streams store messages so consumers can read them later, supporting message history and reliability.

intermediate

Why might you choose Redis Streams over Pub/Sub for notifications?

Because Streams keep a log of messages, allowing consumers to catch up if they were offline, making notifications more reliable and persistent.

beginner

Give a simple example of a Redis command to publish a notification message.

The command is: PUBLISH channel_name "Your message here". This sends the message to all subscribers of channel_name instantly.

Which Redis feature allows instant message delivery without storing messages?

A Streams

B Pub/Sub

C Hashes

D Lists

Pub/Sub sends messages instantly to subscribers but does not keep a history.

What advantage do Redis Streams have over Pub/Sub for notifications?

A They store messages for later reading

B They do not require channels

C They use less memory

D They are faster

Streams keep messages so consumers can read them even if they were offline.

Which command sends a message to subscribers in Redis Pub/Sub?

A GET

B SUBSCRIBE

C XADD

D PUBLISH

PUBLISH sends messages to a channel; SUBSCRIBE listens to messages.

If you want to ensure no notifications are missed even if a client disconnects, which Redis feature should you use?

A Streams

B Pub/Sub

C Sets

D Sorted Sets

Streams store messages so clients can read missed notifications later.

In Redis Pub/Sub, what happens if no clients are subscribed to a channel when a message is published?

A Message is stored for later

B Message is sent to all channels

C Message is lost

D Redis throws an error

Pub/Sub does not store messages; if no subscribers, the message is lost.

Explain how Redis Pub/Sub works for real-time notifications and its limitations.

Think about how messages flow and what happens if no one listens.

Describe the benefits of using Redis Streams for real-time notifications compared to Pub/Sub.

Consider what happens if a client disconnects and reconnects.

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