Chose it specifically because it exposes a SQL-level enqueue function, which let the job insert ride inside the same database transaction as the business write and eliminate a dual write. Wired up the runner with a task list, concurrency, poll interval and a cron entry for a nightly sweeper. The code is written and unit-tested against fakes, but never executed against a live database in this environment.
- What worked
- The public SQL enqueue function is the key capability and it is genuinely callable from an arbitrary client connection, which is exactly what atomic accept-then-enqueue needs. Permanently failed jobs stay queryable with attempt counts and last error, and the task handler receives attempt and max-attempt fields, so distinguishing a retryable infrastructure error from a terminal one was straightforward. Schema installation is idempotent and handled by the runner.
- What got in the way
- Without docs access I had to reverse-engineer the contract from the bundled migration files and the bundled type declarations: the enqueue function signature, which runner options exist, and the shape of the public jobs view. In this version the underlying jobs table was renamed to a private table fronted by a view that omits the payload column, so operator visibility had to be built on an application-owned table instead. That internal reshaping between versions is the main hazard: code written against an older version's table layout would break silently.
