Publisher confirms in RabbitMQ - Time & Space Complexity

Time Complexity: Publisher confirms

O(n)

Understanding Time Complexity

When sending messages with RabbitMQ, publisher confirms help us know if messages reached the broker safely.

We want to understand how the time to confirm messages grows as we send more messages.

Scenario Under Consideration

Analyze the time complexity of the following RabbitMQ publisher confirm code.

channel.confirm_delivery()
for message in messages:
    channel.basic_publish(exchange, routing_key, message)
channel.wait_for_confirms_or_die()

This code sends multiple messages and waits for all confirmations from the broker.

Identify Repeating Operations

Look for repeated actions that affect time.

• Primary operation: Sending each message with basic_publish inside a loop.
• How many times: Once per message, so as many times as messages sent.
• Confirmation wait: wait_for_confirms_or_die waits for all messages at once after sending.

How Execution Grows With Input

As the number of messages grows, the time to send and confirm grows roughly in direct proportion.

Input Size (n)	Approx. Operations
10	About 10 sends + 1 confirm wait
100	About 100 sends + 1 confirm wait
1000	About 1000 sends + 1 confirm wait

Pattern observation: Time grows linearly as messages increase because each message is sent once and confirmed once.

Final Time Complexity

Time Complexity: O(n)

This means the total time grows roughly in direct proportion to the number of messages sent.

Common Mistake

[X] Wrong: "Waiting for confirms only takes constant time regardless of message count."

[OK] Correct: The broker must confirm each message, so waiting time grows with the number of messages sent.

Interview Connect

Understanding how publisher confirms scale helps you design reliable messaging systems that handle load gracefully.

Self-Check

What if we confirmed each message immediately after sending it instead of waiting for all at once? How would the time complexity change?

Practice

1. What does enabling publisher confirms in RabbitMQ do?

easy

A. It automatically retries sending messages on failure.

B. It encrypts messages before sending.

C. It tells you if RabbitMQ accepted your message.

D. It queues messages without sending them.

Solution

1. Step 1: Understand the purpose of publisher confirms

   Publisher confirms notify the sender if the message was accepted by RabbitMQ.

2. Step 2: Compare with other options

   Retrying, encrypting, or queuing without sending are unrelated to confirms.

3. Final Answer:

   It tells you if RabbitMQ accepted your message. -> Option C

4. Quick Check:

   Publisher confirms = message acceptance notification [OK]

Hint: Publisher confirms confirm message acceptance by RabbitMQ [OK]

Common Mistakes:

• Confusing confirms with message encryption
• Thinking confirms retry messages automatically
• Assuming confirms delay message sending

2. Which method must be called on a RabbitMQ channel to enable publisher confirms?

easy

A. enableConfirms()

B. setConfirmMode()

C. startConfirm()

D. confirmSelect()

Solution

1. Step 1: Recall the correct method name

   The method to enable confirms on a channel is confirmSelect().

2. Step 2: Verify other options

   Other method names like enableConfirms() or startConfirm() do not exist in RabbitMQ API.

3. Final Answer:

   confirmSelect() -> Option D

4. Quick Check:

   Enable confirms = confirmSelect() [OK]

Hint: Enable confirms by calling confirmSelect() on the channel [OK]

Common Mistakes:

• Using incorrect method names like enableConfirms()
• Forgetting to call confirmSelect() before publishing
• Confusing confirmSelect() with waitForConfirms()

3. Given this code snippet, what will waitForConfirms() return if the message was accepted?

channel.confirmSelect();
channel.basicPublish(exchange, routingKey, props, body);
boolean confirmed = channel.waitForConfirms();
System.out.println(confirmed);

medium

A. false

B. true

C. null

D. Exception thrown

Solution

1. Step 1: Understand waitForConfirms() behavior

   This method returns true if RabbitMQ accepted the message, false otherwise.

2. Step 2: Given the message was accepted

   The variable confirmed will be true, so printing it outputs 'true'.

3. Final Answer:

   true -> Option B

4. Quick Check:

   Message accepted = waitForConfirms() returns true [OK]

Hint: waitForConfirms() returns true if message accepted [OK]

Common Mistakes:

• Expecting waitForConfirms() to return false on success
• Assuming it returns null or throws exception on success
• Confusing waitForConfirms() with asynchronous callbacks

4. What is wrong with this code snippet for enabling publisher confirms?

channel.basicPublish(exchange, routingKey, props, body);
channel.confirmSelect();
boolean confirmed = channel.waitForConfirms();

medium

A. confirmSelect() must be called before basicPublish()

B. waitForConfirms() cannot be called after publishing

C. basicPublish() requires a callback parameter

D. confirmSelect() should be called after waitForConfirms()

Solution

1. Step 1: Check order of method calls

   confirmSelect() must be called before publishing to enable confirms.

2. Step 2: Identify the error

   In the snippet, confirmSelect() is called after basicPublish(), so confirms are not enabled when publishing.

3. Final Answer:

   confirmSelect() must be called before basicPublish() -> Option A

4. Quick Check:

   Enable confirms before publishing [OK]

Hint: Call confirmSelect() before publishing messages [OK]

Common Mistakes:

• Calling confirmSelect() after publishing
• Thinking waitForConfirms() disables confirms
• Believing basicPublish() needs a callback for confirms

5. You want to ensure your application only proceeds after RabbitMQ confirms message acceptance. Which sequence of calls correctly implements this using publisher confirms?

hard

A. channel.confirmSelect(); channel.basicPublish(...); channel.waitForConfirms();

B. channel.basicPublish(...); channel.waitForConfirms(); channel.confirmSelect();

C. channel.waitForConfirms(); channel.confirmSelect(); channel.basicPublish(...);

D. channel.basicPublish(...); channel.confirmSelect(); channel.waitForConfirms();

Solution

1. Step 1: Enable confirms before publishing

   Call confirmSelect() first to enable confirms on the channel.

2. Step 2: Publish the message and wait for confirmation

   After basicPublish(...), call waitForConfirms() to block until RabbitMQ confirms acceptance.

3. Final Answer:

   channel.confirmSelect(); channel.basicPublish(...); channel.waitForConfirms(); -> Option A

4. Quick Check:

   Enable confirms, publish, then wait [OK]

Hint: Enable confirms, publish, then waitForConfirms() [OK]

Common Mistakes:

• Calling confirmSelect() after publishing
• Waiting for confirms before publishing
• Not calling waitForConfirms() at all