Implementing Delayed Queues in RabbitMQ with TTL and DLX

Background

RabbitMQ does not provide a built‑in delayed‑queue feature, so a queue cannot be declared as a delayed queue directly.

Implementation Approach

Two common solutions exist: using a dedicated plugin or combining existing features. This guide focuses on the latter, leveraging message TTL (time‑to‑live) together with a dead‑letter exchange ( DLX) to emulate a delayed queue.

Use‑Case Example

When an order is placed, if payment is not received within 20 minutes the order should be closed. By configuring RabbitMQ with a 15‑minute TTL, the message is held until it expires, then automatically forwarded to the dead‑letter exchange for later processing.

Configuration Steps

Declare the primary queue with the argument x-message-ttl set to 900000 ms (15 minutes) and specify x-dead-letter-exchange as DLX.

Create the dead‑letter exchange ( DLX) and bind a secondary queue to it.

Implement a consumer that listens on the secondary queue; it will receive the message after the TTL expires, achieving the desired delay.

Result

Messages are retained for the configured TTL, then automatically rerouted to the dead‑letter queue, providing delayed consumption without needing additional plugins.