Correlation ID for matching replies in RabbitMQ - Step-by-Step Execution

Process Flow - Correlation ID for matching replies

Send Request with Correlation ID

↓

Message Broker routes request

↓

Consumer processes request

↓

Consumer sends reply with same Correlation ID

↓

Sender receives reply

↓

Match reply to request using Correlation ID

↓

Process reply

This flow shows how a sender tags a request with a unique Correlation ID, which the consumer copies back in the reply. The sender uses this ID to match replies to requests.

Execution Sample

RabbitMQ

channel.basic_publish(exchange='', routing_key='rpc_queue',
  properties=pika.BasicProperties(correlation_id=corr_id, reply_to=callback_queue),
  body=request_body)

# Later, on receiving reply:
if props.correlation_id == corr_id:
  process_reply(body)

Send a request with a Correlation ID and reply_to queue, then match incoming replies by Correlation ID.

Process Table

Step	Action	Correlation ID	Queue	Result
1	Send request message	abc123	rpc_queue	Message sent with correlation_id=abc123
2	Broker routes message	abc123	rpc_queue	Message delivered to consumer
3	Consumer processes request	abc123	rpc_queue	Request processed
4	Consumer sends reply	abc123	callback_queue	Reply sent with correlation_id=abc123
5	Sender receives reply	abc123	callback_queue	Reply received
6	Match reply to request	abc123	callback_queue	Correlation ID matches, reply processed
7	Check for other replies	none	callback_queue	No more replies, stop

💡 No more replies to process, execution ends

Status Tracker

Variable	Start	After Step 1	After Step 4	After Step 6	Final
corr_id	none	abc123	abc123	abc123	abc123
request_sent	false	true	true	true	true
reply_received	false	false	true	true	true
reply_processed	false	false	false	true	true

Key Moments - 3 Insights

Why must the reply have the same Correlation ID as the request?

The reply uses the same Correlation ID so the sender can match it to the original request, as shown in step 6 of the execution table.

What happens if the Correlation ID does not match any request?

The sender ignores the reply because it cannot match it to a request, preventing confusion or wrong processing (see step 6).

Why do we need a reply_to queue in the request message?

The reply_to queue tells the consumer where to send the reply, enabling the sender to receive it back (step 4).

Visual Quiz - 3 Questions

Look at the execution table, what is the Correlation ID when the consumer sends the reply?

A none

B abc123

C xyz789

D callback_queue

💡 Hint

Check step 4 in the execution table where the consumer sends the reply.

At which step does the sender confirm the reply matches the request?

A Step 2

B Step 3

C Step 6

D Step 5

💡 Hint

Look for the step where correlation ID matching happens in the execution table.

If the reply_to queue was missing in the request, what would change in the execution?

A The sender would not receive the reply

B The consumer would not receive the request

C The reply would not be sent

D The Correlation ID would be lost

💡 Hint

Refer to step 4 and 5 about reply sending and receiving.

Concept Snapshot

Use a unique Correlation ID in request messages to track replies.
Include reply_to queue so consumer knows where to send replies.
Consumer copies Correlation ID in reply.
Sender matches replies by Correlation ID to process correctly.
This avoids confusion when multiple requests are in flight.

Full Transcript

This visual execution shows how a sender uses a Correlation ID to track replies in RabbitMQ. The sender sends a request message with a unique Correlation ID and a reply_to queue. The message broker routes the request to the consumer. The consumer processes the request and sends a reply message back to the reply_to queue, copying the same Correlation ID. The sender listens on the reply_to queue and matches incoming replies by their Correlation ID to the original request. This ensures the sender processes the correct reply for each request. The execution table traces each step from sending the request to processing the reply. Variable tracking shows how the Correlation ID and message states change. Key moments clarify why the Correlation ID and reply_to queue are essential. The quiz tests understanding of these steps and their importance.