Redis as message broker in Django - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the Redis client in Django.

Django

from redis import [1]

Drag options to blanks, or click blank then click option'

ARedis

BClient

CConnection

DBroker

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Client' instead of 'Redis' causes import errors.

Trying to import 'Broker' which does not exist in redis package.

The Redis client class is named Redis. Importing it allows you to connect to the Redis server.

2fill in blank

medium

Complete the code to publish a message to a Redis channel.

Django

redis_client = Redis()
redis_client.[1]('channel1', 'Hello World')

Drag options to blanks, or click blank then click option'

Abroadcast

Bpush

Csend

Dpublish

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'send' or 'push' which are not Redis client methods.

Trying to use 'broadcast' which is not a Redis method.

The method to send a message to a Redis channel is publish. It takes the channel name and the message.

3fill in blank

hard

Fix the error in subscribing to a Redis channel.

Django

pubsub = redis_client.[1]()
pubsub.subscribe('channel1')

Drag options to blanks, or click blank then click option'

Apubsub()

Bsubscribe

Cpubsub

Dpubsub_subscribe

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to call 'subscribe()' directly on the Redis client.

Using 'subscribe' as a method to create pubsub object.

To subscribe, you first create a pubsub object by calling pubsub() on the Redis client. Then you call subscribe() on that object.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that maps channel names to message counts, filtering only channels with more than 5 messages.

Django

message_counts = {channel: count for channel, count in redis_client.[1]('channel_counts').items() if count [2] 5}

Drag options to blanks, or click blank then click option'

Ahgetall

B>

C<

Dkeys

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'keys()' which returns only keys, not counts.

Using '<' which filters counts less than 5.

hgetall('channel_counts') retrieves all fields and values from a Redis hash. The comprehension filters counts greater than 5 using the '>' operator.

5fill in blank

hard

Fill all three blanks to create a Redis message handler that listens to a channel, decodes messages, and prints them.

Django

pubsub = redis_client.[1]()
pubsub.subscribe('[2]')
for message in pubsub.listen():
    if message['type'] == 'message':
        print(message['data'].[3]('utf-8'))

Drag options to blanks, or click blank then click option'

Apubsub

Bchannel1

Cdecode

Dsubscribe

Attempts:

3 left

💡 Hint

Common Mistakes

Calling 'subscribe' instead of 'pubsub()' to create the pubsub object.

Not decoding the message data before printing.

First, create a pubsub object with pubsub(). Then subscribe to the channel named channel1. Finally, decode the message data from bytes to string using decode('utf-8').

Practice

1. What is the main role of Redis when used as a message broker in a Django application?

easy

A. To send messages quickly between different parts of the app

B. To store user passwords securely

C. To serve static files like images and CSS

D. To handle database migrations automatically

Solution

1. Step 1: Understand Redis as a message broker

   Redis acts as a fast messenger that sends messages between parts of an app.

2. Step 2: Identify Redis's role in Django

   In Django, Redis helps different components communicate by sending and receiving messages quickly.

3. Final Answer:

   To send messages quickly between different parts of the app -> Option A

4. Quick Check:

   Redis message broker = fast message sending [OK]

Hint: Remember Redis is for fast message passing, not storage [OK]

Common Mistakes:

• Confusing Redis with database storage
• Thinking Redis serves static files
• Assuming Redis manages migrations

2. Which Django code snippet correctly publishes a message to a Redis channel named updates?

easy

A. redis_client.send('updates', 'New data available')

B. redis_client.subscribe('updates', 'New data available')

C. redis_client.publish('updates', 'New data available')

D. redis_client.receive('updates', 'New data available')

Solution

1. Step 1: Identify the correct Redis method to send messages

   The method to send messages is publish, not subscribe, send, or receive.

2. Step 2: Match method with channel and message

   Using publish('updates', 'New data available') sends the message to the 'updates' channel correctly.

3. Final Answer:

   redis_client.publish('updates', 'New data available') -> Option C

4. Quick Check:

   Send message = publish method [OK]

Hint: Use publish() to send, subscribe() to receive messages [OK]

Common Mistakes:

• Using subscribe() to send messages
• Using non-existent send() or receive() methods
• Mixing up method names

3. Given this code snippet, what will be printed when the message 'Hello everyone' is published to the chat channel?

import redis

r = redis.Redis()

pubsub = r.pubsub()
pubsub.subscribe('chat')

for message in pubsub.listen():
    if message['type'] == 'message':
        print(f"Received: {message['data'].decode()}")
        break

medium

A. Received: Hello everyone

B. Received: message

C. Received: chat

D. No output, code will error

Solution

1. Step 1: Understand the subscription and listening

   The code subscribes to 'chat' channel and listens for messages.

2. Step 2: Decode and print the message data

   When a message is received, it decodes the bytes and prints with prefix 'Received:'.

3. Final Answer:

   Received: Hello everyone -> Option A

4. Quick Check:

   Message data decoded and printed [OK]

Hint: Listen loop prints decoded message data on 'message' type [OK]

Common Mistakes:

• Printing message type instead of data
• Not decoding bytes to string
• Assuming code errors without message

4. You wrote this code to subscribe to Redis messages but your Django app freezes. What is the likely problem?

import redis

r = redis.Redis()

pubsub = r.pubsub()
pubsub.subscribe('notifications')

for message in pubsub.listen():
    print(message)

medium

A. The subscribe() method is missing a callback function

B. The print statement syntax is incorrect

C. Redis server is not running, causing freeze

D. The listen() loop blocks the main thread, freezing the app

Solution

1. Step 1: Analyze the listen() method behavior

   The listen() method blocks and waits for messages, running an infinite loop.

2. Step 2: Understand impact on Django app

   Running this loop in the main thread freezes the app because it never returns control.

3. Final Answer:

   The listen() loop blocks the main thread, freezing the app -> Option D

4. Quick Check:

   Blocking listen() causes freeze [OK]

Hint: Run listen() in background thread to avoid blocking [OK]

Common Mistakes:

• Thinking subscribe() needs a callback
• Assuming Redis server down causes freeze
• Misreading print syntax as error

5. You want to build a Django app that updates the UI in real-time when Redis messages arrive. Which approach best keeps the app responsive while receiving messages?

hard

A. Use Redis publish without subscribing to any channel

B. Run the Redis subscribe listen loop in a separate background thread

C. Call pubsub.listen() directly in the main Django view function

D. Store messages in Django database and poll every minute

Solution

1. Step 1: Identify the need for responsiveness

   The app must stay responsive while waiting for Redis messages.

2. Step 2: Choose non-blocking message listening

   Running the listen loop in a background thread prevents blocking the main app thread.

3. Step 3: Evaluate other options

   Calling listen() in main thread blocks; publishing without subscribing misses messages; polling is slow and inefficient.

4. Final Answer:

   Run the Redis subscribe listen loop in a separate background thread -> Option B

5. Quick Check:

   Background thread keeps app responsive [OK]

Hint: Use background thread for listening to avoid blocking UI [OK]

Common Mistakes:

• Running listen() in main thread causing freeze
• Ignoring subscription and only publishing
• Using slow polling instead of real-time updates