Redis as message broker in Flask - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when a Flask app publishes a message to Redis?

Consider a Flask app using Redis as a message broker. When the app publishes a message to a Redis channel, what is the immediate effect?

Flask

import redis

r = redis.Redis()
r.publish('channel1', 'Hello')

A The message is sent to all clients subscribed to 'channel1' immediately.

B The message is stored in Redis and delivered when clients connect later.

C The message is saved in a Redis list for later retrieval.

D The message triggers a Redis error because publish requires a subscriber.

💡 Hint

Think about how Redis Pub/Sub works with channels and subscribers.

Redis Pub/Sub sends messages instantly to all clients subscribed to the channel. It does not store messages for later delivery or save them in lists.

❓ state_output

intermediate

What is the output of this Redis subscription code in Flask?

Given this Flask code snippet subscribing to a Redis channel, what will be printed when a message is published?

Flask

import redis

r = redis.Redis()
ps = r.pubsub()
ps.subscribe('channel1')

for message in ps.listen():
    if message['type'] == 'message':
        print(message['data'].decode())
        break

A No output because the loop breaks before printing.

B A bytes object representing the message.

C The string 'subscribe' indicating subscription confirmation.

D The exact message string published to 'channel1'.

💡 Hint

Remember the message dictionary keys and their meanings in Redis Pub/Sub.

The 'message' type contains the actual published data. Decoding it prints the original string message.

📝 Syntax

advanced

Which option correctly initializes Redis Pub/Sub in Flask?

Choose the correct way to set up Redis Pub/Sub in a Flask app to listen to a channel.

A

r = redis.Redis()
ps = r.pubsub()
ps.subscribe('channel1')

B

ps = redis.pubsub()
ps.subscribe('channel1')

C

r = redis.Redis()
ps = r.subscribe('channel1')

D ps = redis.Redis().pubsub('channel1')

💡 Hint

Check the Redis Python client API for Pub/Sub setup.

Option A correctly creates a Redis client, then a Pub/Sub object, then subscribes to a channel.

🔧 Debug

advanced

Why does this Flask Redis subscriber never print messages?

Given this code, why does the subscriber never print any messages?

Flask

import redis

r = redis.Redis()
ps = r.pubsub()
ps.subscribe('channel1')

for message in ps.listen():
    if message['type'] == 'message':
        print(message['data'].decode())

A The subscription is missing a call to ps.run() to start listening.

B The Redis server is not running, so no messages arrive.

C The message data is bytes and needs decoding before printing.

D The loop breaks immediately after the first message, so nothing prints.

💡 Hint

Consider the data type of message['data'] and how print handles it.

Redis messages are bytes; printing bytes shows raw bytes, which may appear empty or unreadable. Decoding to string is needed.

🧠 Conceptual

expert

What is a key limitation of using Redis Pub/Sub as a message broker in Flask apps?

Identify the main limitation of Redis Pub/Sub when used as a message broker for Flask applications.

A Messages are encrypted by default, causing performance overhead.

B Messages are not stored; if a subscriber is offline, it misses messages.

C Redis Pub/Sub requires complex setup with multiple Redis instances.

D Redis Pub/Sub only supports JSON messages, limiting data types.

💡 Hint

Think about message delivery guarantees and offline subscribers.

Redis Pub/Sub does not persist messages. Subscribers must be connected to receive messages; otherwise, messages are lost.