Another (non-Rackety) solution is to have your editor do the work for you

The api looks reasonable, although I wonder if it’s possible to have something with multiple back ends to allow other people not to use postgres. Also, I think there are now several job queue libraries and it might be worth thinking about a unification

Thanks for taking a look! The broker side of things is set up so that it can be made generic so adapters for different message queues can definitely be implemented. I’ll probably add at least one for Redis and one for AMQP at some point. Postgres is great for CRUD apps, though, because enqueuing can be transactional: (with-transaction (insert-something!) (enqueue-something!)) . If the transaction succeeds, both objects are guaranteed to have been persisted.