Redis as message broker in Flask - Step-by-Step Execution

Concept Flow - Redis as message broker

Producer sends message

↓

Message stored in Redis list

↓

Consumer polls Redis list

↓

Consumer processes message

↓

Consumer waits for next message

This flow shows how a producer sends messages to Redis, which stores them in a list, and a consumer retrieves and processes them.

Execution Sample

Flask

from flask import Flask
import redis

r = redis.Redis()

# Producer
r.lpush('queue', 'hello')

# Consumer
msg = r.brpop('queue')

This code pushes a message 'hello' to a Redis list 'queue' and then a consumer blocks waiting to pop a message from the same list.

Execution Table

Step	Action	Redis Command	Result	State of 'queue'
1	Producer pushes 'hello'	LPUSH queue 'hello'	1 (list length)	['hello']
2	Consumer blocks waiting	BRPOP queue	Returns ('queue', 'hello')	[] (empty)
3	Consumer processes message	N/A	Message 'hello' processed	[]
4	Consumer waits for next message	BRPOP queue	Blocks waiting	[]

💡 Consumer blocks waiting because queue is empty after popping 'hello'

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4
queue	[]	['hello']	[]	[]	[]
msg	None	None	('queue', 'hello')	('queue', 'hello')	None (waiting)

Key Moments - 2 Insights

Why does the consumer block at step 4?

At step 4, the queue is empty (see execution_table row 4), so BRPOP blocks waiting for new messages to arrive.

What happens to the message after the consumer pops it?

After popping at step 2, the message 'hello' is removed from the queue (execution_table row 2), so the queue becomes empty.

Visual Quiz - 3 Questions

Look at the execution table, what is the state of 'queue' after step 1?

A ['hello']

B []

C ['world']

D None

💡 Hint

Check the 'State of queue' column in execution_table row 1

At which step does the consumer receive the message 'hello'?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at the 'Result' column for when BRPOP returns 'hello' in execution_table

If the producer pushes another message after step 4, what happens to the consumer?

A Consumer crashes

B Consumer ignores the new message

C Consumer immediately receives the new message

D Consumer waits indefinitely

💡 Hint

BRPOP blocks waiting at step 4, so new messages unblock it (see concept_flow)

Concept Snapshot

Redis as message broker uses lists to queue messages.
Producer pushes messages with LPUSH.
Consumer blocks and pops messages with BRPOP.
BRPOP waits if queue is empty.
This enables simple, reliable message passing.

Full Transcript

This visual trace shows how Redis acts as a message broker in a Flask app. The producer uses LPUSH to add messages to a Redis list named 'queue'. The consumer uses BRPOP to block and wait for messages from the same list. When a message is pushed, the consumer unblocks, pops the message, and processes it. If the queue is empty, the consumer waits until a new message arrives. This pattern enables asynchronous communication between parts of an app using Redis as a simple message queue.