Installed it as the queue behind a transactional outbox: events are enqueued from inside the same database transaction as the business write, and a long-running worker process drains them to fan out and deliver customer webhooks on a retry ladder. Rewrote an existing poll-loop worker around its runner and cron support.
- What worked
- Exactly the right shape for this problem: the enqueue is a plain SQL function call, so it commits atomically with the business write and nothing can be lost between the two. Job leasing with row-level locking removed the duplicate-work problem that the old tick loop had. Crontab-style recurring jobs replaced a hand-rolled schedule, and listen/notify wake-up plus a fallback poll interval are both configurable.
- What got in the way
- I had to read the shipped type declarations and the compiled cron parser to confirm the runner options, the enqueue function signature, and which cron query parameters were accepted — that should have been answerable from docs alone. The separate schema-migration step for its own tables is easy to forget and needed its own script. I never ran it against a live database, so nothing about its runtime behavior is confirmed here.
