Work queue for task distribution in RabbitMQ - Step-by-Step Execution

Process Flow - Work queue for task distribution

Producer sends tasks

↓

Tasks enter queue

↓

Multiple workers wait

↓

Worker 1 takes task

↓

Worker 1 processes task

↓

Worker 2 takes next task

↓

Worker 2 processes task

↓

Tasks acknowledged

↓

Queue removes acknowledged tasks

↓

Repeat for new tasks

Tasks are sent by a producer to a queue. Multiple workers listen and take tasks one by one to process and acknowledge. The queue removes tasks only after acknowledgment.

Execution Sample

RabbitMQ

channel.queue_declare(queue='task_queue', durable=True)
channel.basic_publish(exchange='', routing_key='task_queue',
                      body=message, properties=pika.BasicProperties(delivery_mode=2))
channel.basic_consume(queue='task_queue', on_message_callback=callback, auto_ack=False)
channel.start_consuming()

Declare a durable queue, send persistent tasks, and workers consume tasks with manual acknowledgment.

Process Table

Step	Action	Queue State	Worker Action	Acknowledgment	Result
1	Producer declares durable queue	Empty queue created	No worker action	N/A	Queue ready to receive tasks
2	Producer sends Task A	Queue: [Task A]	No worker action	N/A	Task A stored in queue
3	Worker 1 waits and receives Task A	Queue: [] (Task A taken)	Worker 1 processing Task A	No ack yet	Task A removed from queue temporarily
4	Producer sends Task B	Queue: [Task B]	Worker 1 processing Task A	No ack yet	Task B stored in queue
5	Worker 2 waits and receives Task B	Queue: [] (Task B taken)	Worker 2 processing Task B	No ack yet	Task B removed from queue temporarily
6	Worker 1 finishes Task A and sends ack	Queue: []	Worker 1 idle	Ack sent	Task A permanently removed from queue
7	Worker 2 finishes Task B and sends ack	Queue: []	Worker 2 idle	Ack sent	Task B permanently removed from queue
8	No more tasks, workers wait	Queue: []	Workers idle	N/A	Waiting for new tasks

💡 No more tasks in queue, workers wait for new tasks

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6	After Step 7	Final
Queue	[]	[Task A]	[]	[Task B]	[]	[]	[]	[]
Worker 1 State	Idle	Idle	Processing Task A	Processing Task A	Processing Task A	Idle	Idle	Idle
Worker 2 State	Idle	Idle	Idle	Idle	Processing Task B	Processing Task B	Idle	Idle
Acknowledgment Sent	No	No	No	No	No	Yes (Task A)	Yes (Task B)	Yes

Key Moments - 3 Insights

Why does the queue keep the task until the worker sends an acknowledgment?

Because the queue only removes a task after the worker confirms it finished processing (ack). This prevents task loss if a worker crashes before finishing. See steps 3 and 6 in execution_table.

What happens if multiple workers are waiting for tasks?

Tasks are distributed one by one to available workers. Each worker takes a task and processes it independently. See steps 3 and 5 where Worker 1 and Worker 2 take tasks separately.

Why declare the queue as durable and tasks as persistent?

Durable queues and persistent tasks ensure tasks survive RabbitMQ restarts. Without this, tasks could be lost if the server stops unexpectedly. This is shown in the code sample with durable=True and delivery_mode=2.

Visual Quiz - 3 Questions

Look at the execution table, what is the queue state after Worker 1 takes Task A?

A Queue contains Task A and Task B

B Queue still contains Task A

C Queue is empty because Task A is taken

D Queue is deleted

💡 Hint

Check step 3 in the execution_table where Worker 1 takes Task A

At which step does Worker 2 start processing a task?

A Step 4

B Step 5

C Step 2

D Step 6

💡 Hint

Look at Worker 2 State changes in variable_tracker and execution_table rows

If the producer sends a third task after step 7, what will happen to the queue state?

A Queue will contain the new task

B Queue will remain empty

C Queue will delete all tasks

D Workers will stop consuming

💡 Hint

Refer to the flow where new tasks enter the queue and workers consume them

Concept Snapshot

Work queue distributes tasks from producer to multiple workers.
Declare queue durable to survive restarts.
Send tasks as persistent messages.
Workers consume tasks and send manual acknowledgments.
Queue removes tasks only after ack to avoid loss.
Multiple workers share the load by taking tasks one by one.

Full Transcript

In a work queue for task distribution using RabbitMQ, a producer sends tasks to a durable queue. Multiple workers listen to this queue and take tasks one at a time. Each worker processes the task and sends an acknowledgment back to the queue. The queue only removes the task after receiving this acknowledgment, ensuring no task is lost if a worker crashes. Tasks are sent as persistent messages to survive server restarts. This setup balances workload among workers and guarantees reliable task processing.