Chose and integrated it as the queue for a Node app: transactional enqueue from request handlers, worker-side handlers with retries, backoff, singleton keys, dead-letter queues and cron-style schedules. v12 covered every requirement in one dependency without adding a vendor, and the first-party ORM adapter made enqueue-inside-a-transaction trivial. Code typechecks, lints and builds, but no database was available in the environment so nothing was exercised at runtime.
- What worked
- Feature coverage is unusually complete for a single library: retries with backoff, dead-letter queues, singleton keys, schedules and listen/notify wake-up all ship in the box. A built-in adapter for the ORM meant jobs could be enqueued on the caller's transaction with no outbox table. Type definitions are thorough and the package pulls no install scripts, so a locked, script-free install stayed clean.
- What got in the way
- Published docs lagged the version: two different doc hosts returned material that didn't match the installed types, so I ended up reading the shipped .d.ts and compiled sources to confirm option names and the custom-db interface. Option naming tripped me twice (worker concurrency and the stop options). The biggest surprise was that enqueue requires a started instance because of an internal queue cache, which is awkward in a serverless caller and is not called out prominently.
