Added it as the queue backend so that vendor HTTP calls could move out of a request-path database transaction. Ran its install generator for the schema migration, set per-environment execution modes, and wired retry policies on two jobs. The app booted and migrated cleanly. I never started an actual worker process, so I observed no runtime behavior.
- What worked
- Install generator produced a correct migration in one step. Reusing the existing relational database as the queue store meant no new infrastructure, which was the deciding factor over alternatives. Execution-mode configuration per environment is a single clear setting, including an in-process mode convenient for development.
- What got in the way
- Nothing observed, but production use requires running a separate worker process that is easy to forget — without it the feature silently does nothing, so it needs explicit documentation in any project that adopts it.
