Why pub/sub enables real-time messaging in Redis - Performance Analysis

Time Complexity: Why pub/sub enables real-time messaging

O(n)

Understanding Time Complexity

We want to understand how the time it takes to send messages changes as more messages or subscribers are involved in Redis pub/sub.

How does Redis handle sending messages quickly to many listeners?

Scenario Under Consideration

Analyze the time complexity of the following Redis pub/sub commands.

# Subscriber subscribes to a channel
SUBSCRIBE news

# Publisher sends a message to the channel
PUBLISH news "Hello subscribers!"

# Redis delivers the message to all subscribers of 'news'

This code shows how Redis sends a message to all clients subscribed to a channel.

Identify Repeating Operations

Look at what repeats when a message is published.

• Primary operation: Redis sends the message to each subscriber of the channel.
• How many times: Once for each subscriber connected to that channel.

How Execution Grows With Input

As the number of subscribers grows, the work Redis does grows too.

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

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

Final Time Complexity

Time Complexity: O(n)

This means the time to deliver a message grows linearly with the number of subscribers listening to the channel.

Common Mistake

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

[OK] Correct: Redis must send the message to each subscriber, so more subscribers mean more work and more time.

Interview Connect

Understanding how message delivery time grows helps you explain real-time systems clearly and shows you know how scaling affects performance.

Self-Check

"What if Redis used a different method that sends one message to all subscribers at once? How would that change the time complexity?"

Practice

1. What is the main reason Redis Pub/Sub enables real-time messaging?

easy

A. Subscribers must request messages manually.

B. Messages are stored permanently for later retrieval.

C. Messages are sent instantly to all subscribers as soon as they are published.

D. It uses batch processing to send messages every hour.

Solution

1. Step 1: Understand Pub/Sub message delivery

   Redis Pub/Sub sends messages immediately to all clients subscribed to a channel.

2. Step 2: Compare with other messaging methods

   Unlike storing messages or batch sending, Pub/Sub delivers instantly without delay.

3. Final Answer:

   Messages are sent instantly to all subscribers as soon as they are published. -> Option C

4. Quick Check:

   Instant delivery = Real-time messaging [OK]

Hint: Instant delivery means real-time messaging [OK]

Common Mistakes:

• Thinking messages are stored permanently
• Believing subscribers pull messages manually
• Confusing batch sending with real-time

2. Which Redis command is used by a client to subscribe to a channel for real-time messages?

easy

A. SET

B. PUBLISH

C. GET

D. SUBSCRIBE

Solution

1. Step 1: Identify subscription command

   The SUBSCRIBE command tells Redis the client wants to listen to messages on a channel.

2. Step 2: Differentiate from other commands

   PUBLISH sends messages; GET and SET are for key-value operations, not subscriptions.

3. Final Answer:

   SUBSCRIBE -> Option D

4. Quick Check:

   SUBSCRIBE = listen to messages [OK]

Hint: SUBSCRIBE means start listening to a channel [OK]

Common Mistakes:

• Using PUBLISH to subscribe
• Confusing GET/SET with Pub/Sub commands
• Thinking SUBSCRIBE stores messages

3. Consider this Redis Pub/Sub interaction:

Client A: SUBSCRIBE news
Client B: PUBLISH news "Hello World!"

What will Client A receive?

medium

A. "Hello World!" message immediately

B. No message because Client A subscribed after publishing

C. An error message

D. The message after a delay of 10 seconds

Solution

1. Step 1: Analyze subscription timing

   Client A subscribes before Client B publishes, so Client A is listening when message is sent.

2. Step 2: Understand Pub/Sub delivery

   Messages are delivered instantly to all current subscribers on the channel.

3. Final Answer:

   "Hello World!" message immediately -> Option A

4. Quick Check:

   Subscribed before publish = immediate message [OK]

Hint: Subscribers get messages instantly if subscribed before publish [OK]

Common Mistakes:

• Thinking message is delayed
• Assuming message is lost if published after subscribe
• Expecting error on publish

4. You wrote this Redis Pub/Sub code:

SUBSCRIBE sports
PUBLISH sports "Game starts now!"

But your subscriber never receives the message. What is the likely problem?

medium

A. Messages are stored and delivered later, so subscriber must check history.

B. The subscriber must run SUBSCRIBE and listen continuously; mixing commands causes issues.

C. Redis does not support Pub/Sub.

D. PUBLISH command is misspelled.

Solution

1. Step 1: Understand Pub/Sub client behavior

   SUBSCRIBE blocks the client to listen continuously; mixing it with PUBLISH in same client causes no message received.

2. Step 2: Identify correct usage

   Separate clients should SUBSCRIBE and PUBLISH; subscriber must stay connected to receive messages.

3. Final Answer:

   The subscriber must run SUBSCRIBE and listen continuously; mixing commands causes issues. -> Option B

4. Quick Check:

   Separate clients for SUBSCRIBE and PUBLISH [OK]

Hint: SUBSCRIBE blocks; use separate clients for publish and subscribe [OK]

Common Mistakes:

• Running SUBSCRIBE and PUBLISH in same client
• Expecting Redis to store messages
• Assuming misspelled commands cause silent failure

5. You want to build a live notification system using Redis Pub/Sub. Which approach best ensures users get notifications instantly and reliably?

hard

A. Use Pub/Sub for instant delivery and also store notifications in a list for missed messages.

B. Only use Pub/Sub without storing messages; rely on clients always connected.

C. Store all messages in Redis keys and have clients poll every minute.

D. Send notifications via email instead of Pub/Sub.

Solution

1. Step 1: Understand Pub/Sub strengths and limits

   Pub/Sub delivers instantly but does not store messages for offline clients.

2. Step 2: Combine real-time and reliability

   Storing notifications in a list allows clients to fetch missed messages if disconnected.

3. Step 3: Evaluate other options

   Polling causes delay; email is not real-time; relying only on Pub/Sub risks lost messages.

4. Final Answer:

   Use Pub/Sub for instant delivery and also store notifications in a list for missed messages. -> Option A

5. Quick Check:

   Combine Pub/Sub + storage = instant + reliable [OK]

Hint: Combine Pub/Sub with storage for reliability [OK]

Common Mistakes:

• Relying only on Pub/Sub without storage
• Using polling causing delays
• Confusing email with real-time messaging