Real-time notification pattern in Redis - Time & Space Complexity

Time Complexity: Real-time notification pattern

O(n)

Understanding Time Complexity

When using Redis for real-time notifications, it is important to understand how the time to send messages grows as more users or notifications are involved.

We want to know how the system handles more notifications and users efficiently.

Scenario Under Consideration

Analyze the time complexity of the following Redis code snippet.

# Publish a message to a channel
PUBLISH notifications_channel "New message arrived"

# Clients subscribe to the channel
SUBSCRIBE notifications_channel

# Server pushes notifications to all subscribers in real-time

This code sends a notification message to all clients subscribed to a channel instantly.

Identify Repeating Operations

In this pattern, the main repeating operation is the message delivery to each subscriber.

• Primary operation: Delivering the published message to each subscriber.
• How many times: Once per subscriber connected to the channel.

How Execution Grows With Input

The time to deliver notifications grows as the number of subscribers increases.

Input Size (n subscribers)	Approx. Operations
10	10 message deliveries
100	100 message deliveries
1000	1000 message deliveries

Pattern observation: The work grows directly with the number of subscribers; more subscribers mean more message deliveries.

Final Time Complexity

Time Complexity: O(n)

This means the time to send notifications grows linearly with the number of subscribers.

Common Mistake

[X] Wrong: "Publishing a message takes the same time no matter how many subscribers there are."

[OK] Correct: Each subscriber must receive the message, so more subscribers mean more work and longer total delivery time.

Interview Connect

Understanding how notification delivery scales helps you design systems that handle many users smoothly and shows you can think about real-world performance.

Self-Check

"What if we changed from using PUBLISH/SUBSCRIBE to storing notifications in a list for each user? How would the time complexity change?"

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