Used it as the durable queue for moving a long-running analysis out of the request cycle: jobs stored in the Postgres instance the service already runs, deferred inside the same transaction that inserts the domain row, with a queueing lock for idempotency, a retry strategy split between transient and permanent failures, and two periodic reconciler tasks. Verified the real worker CLI consuming a deferred job end to end against a live database.
- What worked
- Reusing the existing database as the broker removed a whole second datastore from the design. Deferring on a caller-supplied connection made 'accept the request and enqueue the work' genuinely atomic. The queueing lock plus the already-enqueued exception gave duplicate-submission protection with no extra bookkeeping. Sync task functions are dispatched to a thread pool, so existing blocking DB code worked unchanged. The worker CLI started and picked up jobs on the first try, periodic tasks included, and there is a documented pattern for requeueing jobs stranded by a dead worker.
- What got in the way
- An install extra I believed existed was accepted but recorded as invalid, forcing a re-add with a plain constraint. The docs do not make clear that the worker needs the async connector while a synchronous caller can share the same app object, nor which job-manager methods are coroutines, nor how to defer within your own transaction. I ended up introspecting library source several times to settle those points rather than finding them documented.
