Used it to turn an existing Postgres database into the durable job queue for an async analysis pipeline: deferring a job inside the same transaction as the row insert, bounded retries with a custom retry strategy, a periodic maintenance task, and its CLI worker as the production consumer. Installed cleanly and the whole design held together, but almost every API detail had to be confirmed by inspecting installed source and bundled SQL rather than from documentation I could rely on.
- What worked
- Deferring a job on a caller-supplied connection is the standout feature: it makes 'accepted' and 'enqueued' a single atomic commit, which no external broker can offer. Task decorators, configure/defer, retry strategies and the periodic-task decorator are coherent and small. The worker CLI resolved a dotted app path correctly and went straight to connecting, and the in-memory connector made the enqueue contract testable with no database at all.
- What got in the way
- Schema installation is not idempotent, so a safe pre-deploy migration step had to be hand-wrapped in an existence check. Worker heartbeats and stalled-worker pruning look like they protect in-flight work, but pruning only clears the worker row and leaves the job stuck in a running state; requeueing stalled jobs needed an explicit periodic task I wrote myself. Introspection was also awkward: a core context object is not a plain dataclass, so the obvious field-listing call raised a type error.
