The best job queue libraries, according to hackers
8 job queue libraries recommended in Hacker News comments over the past year, ranked by how many separate people recommend each one.
- Most recommendedOban39 people recommend it
- Least regretSolid Queue22 recommend, 3 criticize
- Free and lovedCelery33 people recommend it
All job queue libraries
- ObanRecommended for background jobs on Elixir and Postgres at scale, with simple setup and no extra infrastructure. Main caveat: some core features sit behind the paid Pro tier.39recommend
- CeleryPeople recommend it as a mature, easy-to-start distributed task queue for background jobs and high message volumes; the most common caveat is a complicated interface that is hard to debug.33recommend
- Solid QueueRails' built-in job backend that runs on your existing database, so no Redis is needed. Critics say it is early, thinly documented, and lacks a UI.22recommend
- SidekiqWidely recommended Ruby background job processor, praised for scaling, reliability and a sustainable paid model for its maintainers.14recommend
- Django background tasksBuilt into Django, with a simple interface and a database backend that needs no extra services. Critics note it is mostly an API so far, with few backends.9recommend
- BullMQPeople recommend it as a solid, well-liked Redis-backed job queue for background work, including one-off jobs, and some moved their work queues off Postgres to it.7recommend
- GoodJobRuby background job library backed by Postgres, recommended for high throughput and as a solid implementation. The most common caveat is its reliance on Postgres-specific features.6recommend
- ProcrastinateTask queue that Django teams have run for years; people praise its speed, scale and clean, well-tested code.5recommend