Chose it as the job backend specifically because it uses the existing relational database rather than adding a cache server or a second runtime, then added the dependency, an initializer and environment wiring. Never executed: the dependency set could not be installed in this environment, so the install generator and migrations are left as a follow-up step.
- What worked
- Backing onto the database the app already runs removes an entire piece of infrastructure from the deployment, which was the decisive constraint here. Published metadata made the runtime and framework compatibility easy to confirm before committing. Configuration is ordinary framework config with sensible knobs for queues and execution mode.
- What got in the way
- Setup is not purely declarative: it needs a generator run plus a migration before anything works, so the feature cannot be handed over as a code-only change.
