Why pub/sub enables real-time messaging in Redis - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does pub/sub achieve real-time message delivery?

In Redis pub/sub, what is the main reason messages are delivered in real-time to subscribers?

A Subscribers must poll Redis repeatedly to check for new messages, which creates real-time delivery.

B Subscribers receive messages instantly because Redis pushes messages directly to them as soon as they are published.

C Messages are stored in a queue and delivered only when subscribers request them explicitly.

D Redis batches messages and sends them to subscribers at fixed time intervals.

💡 Hint

Think about how messages reach subscribers without delay.

Redis pub/sub pushes messages immediately to all subscribers of a channel, enabling real-time communication without polling or delays.

❓ query_result

intermediate

What output shows a subscriber receiving messages in real-time?

Given a Redis subscriber listening on channel 'news', what output will it show when messages are published?

Redis

SUBSCRIBE news

# Then publisher runs:
PUBLISH news "Hello"
PUBLISH news "World"

A

Subscribed to news channel
Hello
World

B

Hello
World

C

news: Hello
news: World

D

message
news
Hello
message
news
World

💡 Hint

Look at the exact Redis subscriber output format.

Redis subscriber outputs 'message', channel name, then the message for each published message.

📝 Syntax

advanced

Which Redis command syntax correctly subscribes to multiple channels?

Select the correct Redis command to subscribe to channels 'sports' and 'weather' simultaneously.

A SUBSCRIBE sports weather

B SUBSCRIBE sports, weather

C SUBSCRIBE 'sports' 'weather'

D SUBSCRIBE sports; SUBSCRIBE weather

💡 Hint

Redis commands separate multiple channels by spaces, not commas or semicolons.

The correct syntax is SUBSCRIBE followed by channel names separated by spaces without commas or quotes.

❓ optimization

advanced

How to reduce message loss in Redis pub/sub during high load?

Redis pub/sub does not store messages if no subscriber is connected. Which approach helps reduce message loss in real-time messaging?

A Subscribe to channels with pattern matching to catch all messages.

B Increase Redis server memory to buffer more pub/sub messages.

C Use Redis Streams instead of pub/sub to store messages until consumed.

D Publish messages less frequently to avoid overload.

💡 Hint

Think about message persistence and delivery guarantees.

Redis Streams store messages so consumers can read them later, preventing message loss unlike pub/sub which only delivers to active subscribers.

🔧 Debug

expert

Why does this Redis pub/sub subscriber miss some messages?

A subscriber runs SUBSCRIBE on channel 'alerts'. The publisher sends messages rapidly. Sometimes the subscriber misses messages. What is the most likely cause?

Redis

Subscriber:
SUBSCRIBE alerts

Publisher:
for i in range(1000):
  PUBLISH alerts f"Alert {i}"

A Subscriber cannot process messages fast enough, causing message loss because Redis pub/sub does not queue messages.

B Subscriber did not authenticate properly, so messages are blocked.

C Publisher is using wrong channel name, so messages go elsewhere.

D Redis server is down, so messages are lost.

💡 Hint

Consider how Redis pub/sub handles message delivery under load.

Redis pub/sub delivers messages only to connected subscribers instantly. If subscriber is slow, messages sent while it is busy are lost.