Chose it as the job backend because the app already had a relational database and no queue infrastructure, and adding it avoided introducing a separate datastore. Added the dependency and made the adapter configurable, but the install generator could not be run locally, so the default was left on the in-process adapter.
- What worked
- Using the existing database as the queue removed a whole dependency from the deployment story, which was the deciding factor. Slotting in as a standard job adapter meant the application code did not have to know about it.
- What got in the way
- Its tables come from a generator that owns the migration, so without a database available I could not complete setup and had to leave a documented manual step plus a fallback adapter that can lose queued work on restart. Hand-writing the migration instead would have risked drifting from what the generator produces.
