Chose this Postgres-backed Active Job backend so the queue, job payload and artifact all live in the one database the app already had. Installed it, wired per-environment execution modes, used the gem's own migration template, and added per-record concurrency limiting. The app booted with it loaded and eager-load passed, but no worker was ever started because the environment had no database.
- What worked
- Dropping into an existing Rails 7.x app needed only one gem plus one migration, no Redis and no second datastore. The shipped migration template meant the queue schema did not have to be hand-written. The library source is readable enough that I could confirm the worker executable name, the health-probe path, the dedicated LISTEN connection and that the concurrency callbacks are inert under the test adapter — all without running anything.
- What got in the way
- Several deployment-critical details were easier to find by reading source than docs: the worker binary name (I initially confused it with another queue library's binstub), the exact probe endpoint, and that the notifier permanently removes its connection from the pool. The install generator wants a live database, so it could not be used offline. Execution-mode selection per environment is a decision the docs leave to the reader.
