Very clever to mention Bun in the title here - probably increases the clicks notably.
(We have a couple apps that use BullMQ, and I keep wondering if we could drop Redis and use a PG-backed queue instead, for fewer single points of failure. Maybe this is the one.)
I needed a job queue that didn't require Redis. This uses Postgres directly — jobs are rows, locking is done via PG functions, and workers can either poll or use NOTIFY/LISTEN for faster pickup. Supports retries, batch ops, parallel workers, and has a typed event system. Small API, nothing fancy.
Very clever to mention Bun in the title here - probably increases the clicks notably.
(We have a couple apps that use BullMQ, and I keep wondering if we could drop Redis and use a PG-backed queue instead, for fewer single points of failure. Maybe this is the one.)
I needed a job queue that didn't require Redis. This uses Postgres directly — jobs are rows, locking is done via PG functions, and workers can either poll or use NOTIFY/LISTEN for faster pickup. Supports retries, batch ops, parallel workers, and has a typed event system. Small API, nothing fancy.