Installed it to run jobs in Postgres for a transactional outbox and webhook delivery. Jobs were queued with the add_job SQL function inside app transactions and run by a long-lived worker with cron tasks. Tested end to end on a real Postgres: about 65 ms from commit to job start, rolled-back transactions left no jobs, two workers shared 300 jobs and each ran exactly once, cron jobs registered, and shutdown on SIGTERM was clean.
- What worked
- The SQL add_job function made enqueueing inside the same transaction straightforward. SKIP LOCKED claiming meant no double processing across workers. Built-in cron, retries with backoff, and a migrate entry point fit cleanly. It is pure JS, so installing with scripts disabled was fine. The TypeScript types were detailed enough to answer most questions.
- What got in the way
- To check the exact add_job signature, when attempts is incremented, and the crontab option syntax, I had to dig through the compiled dist files and generated SQL. It needs a direct, unpooled connection for LISTEN, which adds a second connection string to configure.
