Precise Order‑Closing Delayed Tasks: Best Practices and Common Pitfalls

Redis Expiration Listening

The Redis documentation states that expired events are generated only when the server actually deletes a key, not when the TTL reaches zero. Redis removes expired keys via periodic offline scans and lazy deletion on access, so expiration notifications can be delayed by minutes and are fire‑and‑forget, meaning clients may miss events during disconnections. Using this mechanism for precise delayed tasks is unreliable and should be avoided.

RabbitMQ Dead‑Letter

RabbitMQ treats a message as a dead letter when it is negatively acknowledged without requeue, exceeds its TTL, or the queue exceeds its maximum length. Configuring a dead‑letter exchange (DLX) and routing key directs such messages to a dead‑letter queue. However, dead‑letter queues do not guarantee delivery timing; messages become dead letters only after the first one does, so later messages may not be processed promptly. The official RabbitMQ delayed‑message‑exchange plugin is recommended for true delayed delivery.

Time Wheel

A time wheel is an efficient in‑memory data structure for scheduling tasks, but most implementations lack persistence. If the process crashes, all scheduled tasks are lost, making it risky for critical delayed operations.

Redisson DelayQueue

Redisson DelayQueue implements a delayed queue using a Redis sorted set (ZSET) where each element’s score is the delivery timestamp. A background scanner runs zrangebyscore to move due messages to a ready list. It guarantees no message loss as long as Redis remains available, and can be combined with database scans as a fallback to mitigate middleware failures.

Conclusion

Prefer message queues with built‑in delayed delivery such as RocketMQ or Pulsar.

If a professional message queue is unavailable, Redisson DelayQueue is a viable Redis‑based alternative, but add compensation mechanisms for Redis outages.

When neither option fits, a time wheel can be used, but ensure robust recovery and database‑scan safeguards.

Never use Redis expiration listening for delayed tasks due to its lack of timing guarantees.