Chose it as a Postgres-backed job queue so the app would not need a second stateful service. Built a job app, a task with a retry strategy, a transactional enqueue that writes the domain row and the queue job on one connection, and worker/schema commands for deployment. Unit tests against its in-memory connector pass; it was never exercised against a real database in this environment.
- What worked
- The feature set fit the problem exactly: deferring a job on a caller-supplied connection makes enqueue atomic with the business write, which removes the dual-write failure mode entirely. Shipping an in-memory connector for tests let me assert on deferred jobs without a database. The retry strategy exposes its decision logic, so I could detect a terminal failure instead of hand-counting attempts.
- What got in the way
- I had to read the installed source repeatedly to settle basic questions — whether connection-scoped defer existed, what the job context fields were, whether attempt counts were zero-based, how the in-memory connector stores jobs. The worst surprise: the CLI rejects the synchronous connector, which is the one the transactional defer path pointed me toward. That would have broken both the worker and the schema step at boot, and nothing warned me until I tried the command. The async connector turns out to serve both paths, but that composition is not obvious.
