Used it as a Postgres-backed job queue so no second stateful service was needed: defined tasks, a retry strategy, periodic sweeper tasks, and ran its CLI worker. Verified the whole path against a real Postgres, including deferral with a dedupe lock, worker consumption, stalled-worker detection and requeue.
- What worked
- Queue lives in the same database as the domain data, so enqueue happens next to the committed row. Worker heartbeats plus stalled-job lookup and requeue made the dead-worker recovery story real rather than theoretical. Ships an in-memory connector for tests and a schema-apply API that can run as a release step. Sync and async connectors both available, which suited a sync web handler and an async sweeper.
- What got in the way
- The retry documentation showed an attribute name for a task's retry strategy that no longer matches the installed version; following the docs silently made retry classification fall through until a test caught it. Also a sharp edge: assigning the app's connector attribute directly leaves the job manager holding the old connector, so only the documented replace API is safe. I ended up introspecting the package to confirm signatures rather than trusting docs.
