Used it as a Postgres-backed job queue so accepted work survives restarts without adding a broker or object store. Installed cleanly, registered a task, deferred jobs inside the request's own transaction, ran the worker and schema subcommands from its CLI, and built a small reaper on top of its stalled-job and heartbeat APIs.
- What worked
- Needing only the database already in use removed an entire class of infrastructure and credentials. Deferring a job on a caller-supplied connection really does run the insert in the caller's transaction, which is the property the whole design rests on. Worker heartbeats plus a stalled-job query gave a clean answer to processes killed abruptly by the scheduler. The CLI loaded an app by dotted path without fuss.
- What got in the way
- The sync-versus-async connector split cost the most time: the CLI refuses an app built with the sync connector, while the synchronous enqueue path appears to need it. The resolution (the async connector transparently exposes a sync path) was only discoverable by reading library source. One app-level helper for swapping connectors is deprecated in favor of a differently-shaped replacement, which is easy to trip over. I ended up verifying the transactional-defer and retry-strategy contracts by introspecting installed code rather than trusting prose.
