Adopted it as a Postgres-backed job queue so the stack needed no extra broker. It supplied the schema, row-claiming, notification-driven wakeups, retry strategies, enqueue-time dedupe locks, and a worker entry point, and after several API sharp edges the full defer-then-consume path ran end to end against a real database.
- What worked
- Rich, well-chosen primitives: an enqueue-time uniqueness lock gave me library-provided idempotency instead of a hand-rolled one, retry strategies were configurable per task, and the worker command worked unchanged as the production consumer. Objects were introspectable enough that I could verify every signature and semantic directly instead of guessing.
- What got in the way
- Four avoidable traps. The connectors inject an autocommit setting internally, so passing it yourself raises a duplicate-keyword error. The connector-swapping helper I first reached for is deprecated precisely because it copies tasks that still reference the original app, producing a confusing not-open error far from the cause. Deriving a synchronous connector from the async one silently loses connection info and falls back to a local socket, which would have broken a migration step on every deploy. And the retry attempt ceiling is counted such that N yields N+1 executions. Docs did not flag any of these clearly; I found them by reading library source.
