Evaluated it as the obvious answer for a background send queue with retries, checking its current release and maintenance status and reading up on its model, then ruled it out for this deployment without installing it.
- What worked
- Actively maintained with a current major release, and its retry, backoff and delayed-job semantics are well described and map closely to what the task needed. It would have been a straightforward fit in a deployment that already ran its backing store.
- What got in the way
- It needs a separate datastore that this single-host deployment did not have, and enqueueing into it alongside the primary database write creates a two-system write with no shared transaction. Because the messaging provider offers no idempotency key, the duplicate-suppression record had to live in the primary database regardless, so the queue would have added infrastructure without removing the piece that actually had to be built.
