Exactly-once processing strategies in RabbitMQ - Step-by-Step Execution

Process Flow - Exactly-once processing strategies

Message Produced

↓

Message Sent to Queue

↓

Consumer Receives Message

↓

Process Message

↓

Acknowledge Message

↓

Commit Processing Result

↓

Message Removed from Queue

↓

Exactly-once Achieved

This flow shows how a message moves from producer to consumer with processing and acknowledgment to ensure it is handled exactly once.

Execution Sample

RabbitMQ

channel.basicConsume(queue, false, consumer);
// process message
channel.basicAck(deliveryTag, false);

Consumer receives a message, processes it, then sends an acknowledgment to RabbitMQ to confirm successful processing.

Process Table

Step	Action	Message State	Acknowledgment Sent	Queue State	Result
1	Producer sends message	In Queue	No	Message in queue	Message ready for consumption
2	Consumer receives message	Being Processed	No	Message reserved, not removed	Message locked for consumer
3	Consumer processes message	Being Processed	No	Message reserved	Processing in progress
4	Consumer sends ack	Processed	Yes	Message removed	Message removed from queue
5	Message processing committed	Processed	Yes	No message	Exactly-once processing ensured
6	Consumer crashes before ack	Being Processed	No	Message requeued	Message redelivered to another consumer
7	Consumer reprocesses message	Being Processed	No	Message reserved	Duplicate processing avoided by idempotency

💡 Message is removed from queue only after acknowledgment, ensuring exactly-once processing.

Status Tracker

Variable	Start	After Step 2	After Step 4	After Step 6	After Step 7
Message State	In Queue	Being Processed	Processed	Being Processed	Being Processed
Acknowledgment Sent	No	No	Yes	No	No
Queue State	Message in queue	Message reserved	Message removed	Message requeued	Message reserved

Key Moments - 3 Insights

Why doesn't RabbitMQ remove the message immediately when the consumer receives it?

Because the message is only removed after the consumer sends an acknowledgment (see Step 4 in execution_table). This prevents message loss if the consumer crashes during processing.

What happens if the consumer crashes before sending an acknowledgment?

The message is requeued and delivered again to another consumer (see Step 6). This ensures the message is not lost but may cause duplicate processing if not handled carefully.

How do we avoid processing the same message twice when it is redelivered?

By making the processing idempotent or using unique message IDs to detect duplicates (refer to Step 7). This is key to exactly-once processing.

Visual Quiz - 3 Questions

Look at the execution_table, at which step is the message removed from the queue?

A Step 4

B Step 2

C Step 6

D Step 1

💡 Hint

Check the 'Queue State' column for when the message changes from reserved to removed.

According to variable_tracker, what is the acknowledgment state after Step 6?

A Yes

B Unknown

C No

D Pending

💡 Hint

Look at the 'Acknowledgment Sent' row under 'After Step 6' column.

If the consumer never sends an acknowledgment, what happens to the message according to the execution_table?

A Message stays in queue forever

B Message is requeued and redelivered

C Message is lost

D Message is deleted automatically

💡 Hint

Refer to Step 6 where the consumer crashes before ack.

Concept Snapshot

Exactly-once processing in RabbitMQ means each message is processed one time only.
Producer sends message to queue.
Consumer receives and processes message but does NOT remove it immediately.
Consumer sends acknowledgment after successful processing.
Message is removed only after ack, preventing loss or duplicates.
Idempotent processing helps handle redelivered messages safely.

Full Transcript

Exactly-once processing strategies in RabbitMQ ensure that each message is processed a single time without loss or duplication. The producer sends a message to the queue. The consumer receives the message and processes it but the message remains in the queue until the consumer sends an acknowledgment. Only after the acknowledgment does RabbitMQ remove the message from the queue. If the consumer crashes before sending the acknowledgment, the message is requeued and delivered again to another consumer. To avoid duplicate processing, consumers should implement idempotent processing or use unique message IDs. This flow guarantees that messages are processed exactly once, even in failure scenarios.