Delivery Confirmation

Delivery confirmation provides publisher-side acknowledgement that a message has been accepted by RabbitMQ.

This mechanism improves reliability and helps detect delivery failures.

---

Publish Flow

sequenceDiagram

    participant Publisher

    participant RabbitMQ

    Publisher->>RabbitMQ: Publish Message

    RabbitMQ-->>Publisher: Ack

---

Why Use Delivery Confirmation?

Without confirmations:

Publisher
    ->
Network Failure
    ->
Unknown Result

The publisher cannot determine whether the message was accepted.

With confirmations:

Publisher
    ->
RabbitMQ Ack

The publisher receives explicit feedback.

---

Typical Scenarios

Delivery confirmations are recommended for:

• financial systems;
• integration platforms;
• business-critical workflows;
• audit pipelines.

---

Performance Considerations

Confirmations introduce additional network round-trips.

Trade-offs:

Benefit	Cost
Higher reliability	Slightly lower throughput
Failure detection	Additional latency

---

Descriptor Integration

Delivery confirmation behavior can be configured through descriptor settings.

This allows:

• environment-specific reliability policies;
• centralized configuration;
• consistent publisher behavior.

The exact descriptor properties are documented in the Reference section.