Headers exchange in RabbitMQ - Step-by-Step Execution

Process Flow - Headers exchange

Message Published with Headers

↓

Headers Exchange Receives Message

↓

Check Binding Headers

↓

Route to Queue

A message with headers is sent to the headers exchange, which checks if the message headers match the binding headers of queues. If they match, the message is routed to those queues; otherwise, it is discarded.

Execution Sample

RabbitMQ

1. Publish message with headers: {"format":"pdf", "type":"report"}
2. Headers exchange checks bindings:
   - Queue1 binding: {"format":"pdf"}
   - Queue2 binding: {"type":"invoice"}
3. Message routed to Queue1 only

This example shows a message with headers being routed only to the queue whose binding headers match the message headers.

Process Table

Step	Message Headers	Binding Headers Checked	Match Result	Action
1	{"format":"pdf", "type":"report"}	Queue1: {"format":"pdf"}	Match	Route message to Queue1
2	{"format":"pdf", "type":"report"}	Queue2: {"type":"invoice"}	No Match	Do not route to Queue2
3	N/A	All bindings checked	N/A	Routing complete

💡 All binding headers checked; message routed only to matching queues.

Status Tracker

Variable	Start	After Step 1	After Step 2	Final
Message Headers	{}	{"format":"pdf", "type":"report"}	{"format":"pdf", "type":"report"}	{"format":"pdf", "type":"report"}
Queues Routed	[]	[Queue1]	[Queue1]	[Queue1]

Key Moments - 2 Insights

Why does the message route only to Queue1 and not Queue2?

Because the message headers match Queue1's binding headers ({"format":"pdf"}) but do not match Queue2's binding headers ({"type":"invoice"}), as shown in execution_table rows 1 and 2.

What happens if no binding headers match the message headers?

The message is discarded or dropped by the headers exchange since no queues match, as implied by the 'No Match' branch in the concept_flow.

Visual Quiz - 3 Questions

Look at the execution_table, at Step 2, what is the match result for Queue2?

A Match

B No Match

C Partial Match

D Not Checked

💡 Hint

Check the 'Match Result' column in execution_table row 2.

At which step does the message get routed to Queue1?

A Step 3

B Step 2

C Step 1

D Never

💡 Hint

Look at the 'Action' column in execution_table row 1.

If the message headers changed to {"type":"invoice"}, which queue would it route to?

A Queue2 only

B Queue1 only

C Both Queue1 and Queue2

D No queues

💡 Hint

Compare message headers with binding headers in execution_table and concept_flow.

Concept Snapshot

Headers Exchange in RabbitMQ:
- Routes messages based on matching headers.
- Message headers compared to queue binding headers.
- If headers match, message routed to that queue.
- Supports complex routing without routing keys.
- Useful for flexible, attribute-based routing.

Full Transcript

In RabbitMQ, a headers exchange routes messages by comparing the message's headers to the binding headers of queues. When a message is published with headers, the exchange checks each queue's binding headers. If the message headers match a queue's binding headers, the message is routed to that queue. If no match is found, the message is discarded. For example, a message with headers {"format":"pdf", "type":"report"} matches a queue bound with {"format":"pdf"} but not one bound with {"type":"invoice"}. This allows flexible routing based on message attributes rather than routing keys.