Used as the Postgres-backed ActiveJob backend so accepted work survives host replacement, with polling worker, retries, and dashboard. Setup was compact, but retry exhaustion semantics, backoff options, and idempotency edge cases took iteration and live worker verification helped.
- What worked
- Postgres-backed durability, continuous worker consumption, and dashboard visibility matched the no-extra-datastore goal.
- What got in the way
- Retry versus discard behavior and delay options were unclear at first and surfaced only through test failures.
