Redis as message broker in Flask - Performance & Optimization

Performance: Redis as message broker

MEDIUM IMPACT

This affects the responsiveness and throughput of message passing between components in a web application.

Passing messages between Flask app components asynchronously

Flask

import redis
from flask import Flask
app = Flask(__name__)
r = redis.Redis()

@app.route('/send/<msg>')
def send(msg):
    r.lpush('messages', msg)
    return 'Message sent'

@app.route('/receive')
def receive():
    msg = r.rpop('messages')
    return msg.decode() if msg else 'No messages'

Offloads message storage and retrieval to Redis, enabling non-blocking, fast message passing.

📈 Performance GainNon-blocking IO; reduces main thread load; supports high concurrency

Passing messages between Flask app components asynchronously

Flask

from flask import Flask
app = Flask(__name__)

messages = []

@app.route('/send/<msg>')
def send(msg):
    messages.append(msg)
    return 'Message sent'

@app.route('/receive')
def receive():
    if messages:
        return messages.pop(0)
    return 'No messages'

Storing messages in a list in memory blocks the main thread and does not scale well under load.

📉 Performance CostBlocks rendering for each message; causes slow response under concurrent requests

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
In-memory message queue in Flask	None	Blocks main thread	Delays response rendering	[X] Bad
Redis message broker with Flask	None	Non-blocking	Fast response rendering	[OK] Good

Rendering Pipeline

Using Redis as a message broker moves message handling outside the Flask app process, reducing blocking during request handling.

→Interaction Handling

→Network IO

→JavaScript Event Loop

⚠️ BottleneckInteraction Handling when using in-memory message queues

Core Web Vital Affected

INP

This affects the responsiveness and throughput of message passing between components in a web application.

Optimization Tips

1Use Redis to handle message queues outside the Flask main thread.

2Avoid in-memory message queues that block request handling.

3Monitor interaction responsiveness (INP) when implementing message brokers.

Performance Quiz - 3 Questions

What is a key performance benefit of using Redis as a message broker in a Flask app?

A It increases the size of the Flask app bundle.

B It offloads message handling from the main thread, reducing blocking.

C It causes more DOM reflows during message passing.

D It delays the first contentful paint.

DevTools: Performance

How to check: Record a session sending and receiving messages; observe main thread activity and request durations.

What to look for: Look for reduced main thread blocking and faster request completion times with Redis.

Practice

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

easy

A. To serve static files like images and CSS

B. To store user passwords securely

C. To send and receive messages between different parts of the app

D. To handle HTTP requests directly

Solution

1. Step 1: Understand Redis as a message broker

   Redis acts as a middleman to send messages between parts of an app, enabling communication.

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

   It is not used for storing passwords, serving files, or handling HTTP requests directly.

3. Final Answer:

   To send and receive messages between different parts of the app -> Option C

4. Quick Check:

   Redis message broker = send/receive messages [OK]

Hint: Redis in Flask is for messaging, not storage or HTTP [OK]

Common Mistakes:

• Confusing Redis with a database for user data
• Thinking Redis serves static files
• Assuming Redis handles HTTP requests

2. Which of the following is the correct way to publish a message to a Redis channel in Flask?

easy

A. redis_client.post('channel', 'message')

B. redis_client.send('channel', 'message')

C. redis_client.push('channel', 'message')

D. redis_client.publish('channel', 'message')

Solution

1. Step 1: Recall Redis publish method

   Redis uses the method publish to send messages to a channel.

2. Step 2: Check method names

   Only publish is the correct Redis command; others like send, push, or post are incorrect.

3. Final Answer:

   redis_client.publish('channel', 'message') -> Option D

4. Quick Check:

   Publish method = publish() [OK]

Hint: Use publish() to send messages in Redis [OK]

Common Mistakes:

• Using send() instead of publish()
• Confusing push() with publish()
• Trying to use post() which is not a Redis method

3. Given the following Flask code snippet using Redis, what will be printed when a message is published to 'test_channel'?

import redis
r = redis.Redis()

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

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

medium

A. The published message content decoded as a string

B. The string 'test_channel'

C. The message type 'subscribe'

D. An error because decode() is not valid here

Solution

1. Step 1: Understand pubsub.listen() behavior

   The loop listens for messages on 'test_channel'. When a message of type 'message' arrives, it prints the decoded data.

2. Step 2: Decode message data

   The message data is bytes, so decode() converts it to a string, which is printed.

3. Final Answer:

   The published message content decoded as a string -> Option A

4. Quick Check:

   Message data decoded = printed string [OK]

Hint: listen() yields messages; decode bytes to string before print [OK]

Common Mistakes:

• Printing channel name instead of message data
• Confusing message type 'subscribe' with 'message'
• Forgetting to decode bytes to string

4. What is the main issue with this Flask Redis subscriber code snippet?

import redis
r = redis.Redis()
pubsub = r.pubsub()
pubsub.subscribe('channel')

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

It causes the Flask app to freeze and not respond.

medium

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

B. The decode() method is called on a string, causing an error

C. The subscribe() method is missing required parameters

D. Redis client is not connected to the server

Solution

1. Step 1: Analyze listen() behavior

   The listen() method blocks execution, waiting for messages indefinitely.

2. Step 2: Understand Flask app impact

   Running listen() in the main thread stops Flask from handling other requests, freezing the app.

3. Final Answer:

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

4. Quick Check:

   Blocking listen() = app freeze [OK]

Hint: listen() blocks; run it in background thread [OK]

Common Mistakes:

• Thinking decode() causes error here
• Believing subscribe() needs extra parameters
• Assuming Redis connection is missing without error

5. You want to listen for Redis messages in a Flask app without freezing it. Which approach correctly solves this problem?

hard

A. Call pubsub.listen() directly in the main Flask route handler

B. Run the Redis pubsub.listen() loop inside a background thread

C. Use Redis publish() inside the listen() loop

D. Subscribe to Redis channels without calling listen()

Solution

1. Step 1: Identify blocking issue with listen()

   Calling listen() in the main thread blocks Flask, freezing the app.

2. Step 2: Use background thread for listening

   Running listen() in a separate thread allows Flask to stay responsive while listening for messages.

3. Final Answer:

   Run the Redis pubsub.listen() loop inside a background thread -> Option B

4. Quick Check:

   Background thread for listen() = no freeze [OK]

Hint: Use background thread to avoid blocking Flask [OK]

Common Mistakes:

• Running listen() in main route causing freeze
• Misusing publish() inside listen() loop
• Subscribing without listen() so no messages received