A PostgreSQL reaper is my default for expiring stale property reservations; use a queue delay when the hold must trigger work at high volume or outside the reservation database. The deciding feature is recovery, not timer precision. A reservation that remains held after its fixed window is operational debt: it blocks inventory, confuses staff, and may produce a duplicate reminder when a retry races the original delivery.
The implementation should record an absolute expires_at , claim work transactionally, and make the expiry operation idempotent. A delayed message is only a wake-up hint. The database remains the authority.
The queue is not the clock.
How should I implement delayed reminders using a message queue?
For a property system, compare two designs. A PostgreSQL reaper periodically selects expired holds, claims a bounded batch, and releases them. It is easy to inspect with ordinary SQL, and recovery is a restart plus another scan.…