Solid Queue
Hacker ApprovedRanked 3 of 8 job queue libraries by recommenders
Rails' 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.
Rails' 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.
25 people gave an opinion
- recommend it
- 22
- criticize it
- 3
- approval share
- 88%
Recommended in 5 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: recommended
- September 2026: recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Why it carries the badge
- 22 people recommend itNeeds 10 or more, met.
- 7.3 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 5 of 13 monthsNeeds 4 or more, 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
Runs on your database, no Redis
“it's really cool to have something that is native to the platform and has no dependencies beyond Postgres”
Comment from 1 Aug 2026 in “Solid Queue 1.6.0 now supports fiber workers” “defaulting to the DB for queue (SolidQueue) / caching (SolidCache), such a nice out of the box experience”
Comment from 9 Sep 2026 in “Rails 8 Guide: Features, Requirements and Upgrade Path (2026)” “makes it possible, and fairly smooth, to configure to use the same db”
Comment from 14 Jan 2026 in “I Love You, Redis, but I'm Leaving You for SolidQueue” - Comment from 10 Aug 2026 in “Ask HN: What are you working on? (August 2026)”
Rails default with good out-of-box setup
“defaulting to the DB for queue (SolidQueue) / caching (SolidCache), such a nice out of the box experience”
Comment from 9 Sep 2026 in “Rails 8 Guide: Features, Requirements and Upgrade Path (2026)” “it's got easier if you stick to the rails-provided tooling”
Comment from 9 Sep 2026 in “Rails 8 Guide: Features, Requirements and Upgrade Path (2026)” “a solid handful of great features you get out of the box”
Comment from 14 Jan 2026 in “I Love You, Redis, but I'm Leaving You for SolidQueue” Fiber mode needs far fewer connections
“The difference is staggering when you compare to threaded mode: it requires 1,320 database connections to run the same benchmark that the fiber mode runs with 60.”
Comment from 1 Aug 2026 in “Solid Queue 1.6.0 now supports fiber workers” “upstreaming important work about fiber usage into Rails Solid Queue so that we reap the Async benefits”
Comment from 1 Sep 2026 in “Fastpotify” “So much of work that goes onto work queues is IO bound, and fibers are a great fit for that.”
Comment from 1 Aug 2026 in “Solid Queue 1.6.0 now supports fiber workers” Handles about 20M jobs daily cheaply
“doing about 20M jobs/day on a $45/mo VM with plenty of room to spare”
Comment from 28 Jan 2026 in “Oban, the job processing framework from Elixir, has come to Python” “you've probably got a very large runway with SolidQueue”
Comment from 14 Jan 2026 in “I Love You, Redis, but I'm Leaving You for SolidQueue”
What people warn about
Each mark is one comment
Early-stage and thinly documented
“it's still early days software despite the marketing”
Comment from 14 Jan 2026 in “I Love You, Redis, but I'm Leaving You for SolidQueue” “Documentation doesn't really cover the case”
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 QueueThis page | 22 | 3 | 88% | 5 | — | Approved |
| Sidekiq | 14 | 3 | 82% | 7 | — | Approved |
| Django background tasks | 9 | 3 | 75% | 3 | — | — |
What people said
24 of the 27 comments that mention it, newest first. Each links to the original comment.
“Solid queue, cache, Active Storage with Turbo Frames give you all the benefits of single-page interactivity”
“it's got easier if you stick to the rails-provided tooling”
“defaulting to the DB for queue (SolidQueue) / caching (SolidCache), such a nice out of the box experience”
“upstreaming important work about fiber usage into Rails Solid Queue so that we reap the Async benefits”
“No Redis or anything to have to wrangle.”
“it's really cool to have something that is native to the platform and has no dependencies beyond Postgres”
“So much of work that goes onto work queues is IO bound, and fibers are a great fit for that.”
“As someone who spent 15+ years doing Ruby/Rails, it’s nice to see this land.”
“The difference is staggering when you compare to threaded mode: it requires 1,320 database connections to run the same benchmark that the fiber mode runs with 60.”
“doing about 20M jobs/day on a $45/mo VM with plenty of room to spare”
“I really enjoyed learning about the internals of Solid Queue”
“it's still early days software despite the marketing”
“a solid handful of great features you get out of the box”
“One thing I don't like about SolidQueue is the lack of solid UI.”
“makes it possible, and fairly smooth, to configure to use the same db”
“I like that SolidQueue works with multiple databases. Too bad it needs rails.”
“Documentation doesn't really cover the case”
“The primary pain point I see here is if devs lean into transactions such that their job is only created together with the everything else that happened.”
“you've probably got a very large runway with SolidQueue”
“it is easy to hit the wall even with 10 or so workers”
“Basecamp is a MySQL shop and their policy is not to accept RDMS engine specific queries”
“from what i’ve seen so far, solidqueue doesn’t make this separation.”
“Every time some production environment can be simplified, it is good news in my opinion.”
“which has given me no stress in dev”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.