Chose this Postgres-backed job backend for an app with no Redis and a conservative language-version floor, then wired it in: install generator produced the schema migration, an initializer set queue/thread/shutdown behavior, and the bundled ops dashboard was mounted behind basic auth. The app booted with the adapter active in both development and eager-loaded production modes.
- What worked
- Runs entirely on the existing relational database, so no new infrastructure was needed. Broad language-version support made it the only viable choice against the project's floor. The install generator worked on the first run. The dashboard ships its own frontend assets and served them without any asset pipeline, which mattered in this stripped-down app. Source and configuration defaults were readable and consistent with the documented environment variables.
- What got in the way
- Several load-bearing defaults were not stated plainly in the README and had to be confirmed by reading the configuration source: the shutdown timeout defaults to waiting forever (bad for container deploys), the worker thread count silently inherits a generic server-thread variable when its own is unset, and the transaction-commit enqueue default is the single behavior the whole durability design rests on. Those deserve prominent callouts rather than source-diving.
