Chose it as the queue backend because it reuses the existing relational database and avoids adding a second datastore for roughly forty jobs a week, then wired the adapter per environment and documented the install steps. Never installed or ran, since neither the dependency install nor a database was available here.
- What worked
- Using the primary database as the queue is exactly the right trade at this volume, and the adapter configuration is a one-line per-environment change. Documented setup is short and the operational story needs no extra service.
- What got in the way
- Its tables come from a generator, so the schema cannot be completed without running the install task against a live database. That left a hand-off step the developer must run themselves, and the checked-in schema dump is incomplete until they do.
