GoodJob
Ranked 7 of 8 job queue libraries by recommenders
Ruby 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.
Ruby 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.
7 people gave an opinion
- recommend it
- 6
- criticize it
- 1
- approval share
- 86%
Recommended in 2 of 13 months
- November 2025: not recommended
- December 2025: not recommended
- January 2026: recommended
- February 2026: not recommended
- March 2026: recommended
- April 2026: not recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 6 people recommend itNeeds 10 or more, not met.
- 6 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 2 of 13 monthsNeeds 4 or more, not met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Solid, strong implementation
“Good Job is a strong attempt.”
Comment from 28 Jan 2026 in “Oban, the job processing framework from Elixir, has come to Python” “are solid implementations”
Comment from 11 Mar 2026 in “Ask HN: Do you still run Redis and workers just for background jobs?”
What people warn about
Each mark is one comment
Uses Postgres-specific features
“The main blocker for me with GoodJob is that it uses certain pg-specific features”
Comment from 14 Jan 2026 in “I Love You, Redis, but I'm Leaving You for SolidQueue”
Other job queue libraries people recommend
The four most recommended other job queue libraries, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Oban | 39 | 8 | 83% | 8 | — | Approved |
| Celery | 33 | 38 | 46% | 8 | — | — |
| Solid Queue | 22 | 3 | 88% | 5 | — | Approved |
| Sidekiq | 14 | 3 | 82% | 7 | — | Approved |
| GoodJobThis page | 6 | 1 | 86% | 2 | — | — |
What people said
8 of the 10 comments that mention it, newest first. Each links to the original comment.
“are solid implementations”
“Good Job is a strong attempt.”
“allows for very high throughput”
“Ah neat, I didn't realize GoodJob had batches, great.”
“For new projects, I might be more biased towards GoodJob.”
“The main blocker for me with GoodJob is that it uses certain pg-specific features”
“good_job is the ideal approach to a PG backed queue.”
“Redis beats everything else for the above usecase.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.