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.

Practice

1. What is the main purpose of a headers exchange in RabbitMQ?

easy

A. Route messages based on message headers instead of routing keys

B. Route messages only by exact routing key matches

C. Store messages temporarily before delivery

D. Encrypt messages for secure transmission

Solution

1. Step 1: Understand the role of headers exchange

   A headers exchange routes messages by inspecting the headers attached to the message, not by routing keys.

2. Step 2: Compare with other exchange types

   Unlike direct or topic exchanges that use routing keys, headers exchange uses message headers for routing decisions.

3. Final Answer:

   Route messages based on message headers instead of routing keys -> Option A

4. Quick Check:

   Headers exchange = header-based routing [OK]

Hint: Headers exchange routes by headers, not keys [OK]

Common Mistakes:

• Confusing headers exchange with direct exchange
• Thinking routing keys are used for headers exchange
• Assuming headers exchange stores messages
• Believing headers exchange encrypts messages

2. Which of the following is the correct way to declare a headers exchange named my_headers using RabbitMQ's AMQP protocol?

easy

A. channel.bind_exchange(exchange='my_headers', type='headers')

B. channel.exchange_declare(exchange='my_headers', exchange_type='headers')

C. channel.queue_declare(queue='my_headers', durable=True)

D. channel.exchange_declare(exchange='my_headers', exchange_type='direct')

Solution

1. Step 1: Identify the correct method to declare an exchange

   In RabbitMQ's AMQP, exchange_declare is used to create exchanges.

2. Step 2: Check the exchange type for headers exchange

   The exchange type must be set to headers to create a headers exchange.

3. Final Answer:

   channel.exchange_declare(exchange='my_headers', exchange_type='headers') -> Option B

4. Quick Check:

   Declare headers exchange with exchange_type='headers' [OK]

Hint: Use exchange_type='headers' to declare headers exchange [OK]

Common Mistakes:

• Using queue_declare instead of exchange_declare
• Setting exchange_type to 'direct' or other types
• Trying to bind exchange instead of declaring it
• Misspelling exchange_type parameter

3. Given a headers exchange with a queue bound using headers {'x-match': 'all', 'format': 'pdf', 'type': 'report'}, which message headers will be routed to this queue?

medium

A. {'format': 'doc', 'type': 'report'}

B. {'format': 'pdf', 'type': 'invoice'}

C. {'format': 'pdf', 'priority': 'high'}

D. {'format': 'pdf', 'type': 'report'}

Solution

1. Step 1: Understand the meaning of 'x-match': 'all'

   With x-match set to all, all specified headers must exactly match the message headers.

2. Step 2: Compare each option's headers with the binding headers

   {'format': 'pdf', 'type': 'report'} matches both 'format': 'pdf' and 'type': 'report' exactly. {'format': 'pdf', 'type': 'invoice'} mismatches 'type'. {'format': 'pdf', 'priority': 'high'} misses the required 'type': 'report'. {'format': 'doc', 'type': 'report'} mismatches 'format'.

3. Final Answer:

   {'format': 'pdf', 'type': 'report'} -> Option D

4. Quick Check:

   x-match='all' means all headers must match exactly [OK]

Hint: x-match='all' requires all headers to match exactly [OK]

Common Mistakes:

• Assuming extra headers prevent matching
• Confusing 'all' with 'any' in x-match
• Ignoring missing required headers
• Mixing up header keys and values

4. You have a headers exchange with a queue bound using {'x-match': 'any', 'format': 'pdf', 'type': 'report'}. A message with headers {'format': 'doc', 'type': 'invoice'} is sent. Why does the message not reach the queue?

medium

A. Because the message headers are missing the 'x-match' key

B. Because x-match must be 'all' to match any header

C. Because none of the headers match the binding criteria

D. Because headers exchange only matches routing keys

Solution

1. Step 1: Understand x-match='any' behavior

   With x-match set to any, the message must match at least one of the specified headers.

2. Step 2: Check message headers against binding headers

   The message headers are 'format': 'doc' and 'type': 'invoice'. Neither matches 'format': 'pdf' nor 'type': 'report'. So no header matches.

3. Final Answer:

   Because none of the headers match the binding criteria -> Option C

4. Quick Check:

   x-match='any' requires at least one header match [OK]

Hint: At least one header must match with x-match='any' [OK]

Common Mistakes:

• Thinking x-match='all' is required for any match
• Assuming message needs x-match header
• Confusing headers exchange with routing key matching
• Ignoring header value differences

5. You want to route messages to two different queues from a headers exchange: one queue should receive messages where format is pdf and type is report (both must match), and the other queue should receive messages where either priority is high or department is sales. How should you bind these queues to the headers exchange?

hard

A. Bind queue1 with {'x-match':'all', 'format':'pdf', 'type':'report'} and queue2 with {'x-match':'any', 'priority':'high', 'department':'sales'}

B. Bind queue1 with {'x-match':'any', 'format':'pdf', 'type':'report'} and queue2 with {'x-match':'all', 'priority':'high', 'department':'sales'}

C. Bind both queues with {'x-match':'all', 'format':'pdf', 'type':'report', 'priority':'high', 'department':'sales'}

D. Bind queue1 with {'format':'pdf', 'type':'report'} and queue2 with {'priority':'high', 'department':'sales'} without x-match

Solution

1. Step 1: Determine binding for queue1 requiring both headers

   Since both 'format' and 'type' must match, use x-match: all with those headers.

2. Step 2: Determine binding for queue2 requiring either header

   Since either 'priority' or 'department' must match, use x-match: any with those headers.

3. Step 3: Verify options

   Bind queue1 with {'x-match':'all', 'format':'pdf', 'type':'report'} and queue2 with {'x-match':'any', 'priority':'high', 'department':'sales'} correctly sets x-match for each queue's binding. Bind queue1 with {'x-match':'any', 'format':'pdf', 'type':'report'} and queue2 with {'x-match':'all', 'priority':'high', 'department':'sales'} reverses 'all' and 'any'. Bind both queues with {'x-match':'all', 'format':'pdf', 'type':'report', 'priority':'high', 'department':'sales'} combines all headers with 'all' which is incorrect. Bind queue1 with {'format':'pdf', 'type':'report'} and queue2 with {'priority':'high', 'department':'sales'} without x-match omits x-match which defaults to 'all' but is ambiguous.

4. Final Answer:

   Bind queue1 with {'x-match':'all', 'format':'pdf', 'type':'report'} and queue2 with {'x-match':'any', 'priority':'high', 'department':'sales'} -> Option A

5. Quick Check:

   Use x-match='all' for all headers, 'any' for any header [OK]

Hint: Use x-match='all' for all headers, 'any' for any header [OK]

Common Mistakes:

• Mixing up 'all' and 'any' in bindings
• Not specifying x-match leading to wrong defaults
• Combining unrelated headers in one binding
• Assuming missing x-match means 'any'