{"slug": "solidqueue", "name": "SolidQueue", "category": "other", "category_name": "Other software", "description": "", "recommenders": 1, "commenters": 4, "warners": 1, "score": 0.644, "rising": -0.33, "first": "2026-01-14", "latest": "2026-08-01", "why": "This looks fantastic for a common async workflow I use.", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 1, "neutral": 2, "compare": 0, "warn": 1}, "spark": [0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0, 0], "listed": false, "loved": [], "caveat": "", "short_quote": "This looks fantastic for a common async workflow I use.", "icon": false, "domain": null, "github_repo": "github.com/rails/solid_queue", "official_url": "https://github.com/rails/solid_queue", "pricing": "", "aliases": ["SolidQueue", "Solid Queue"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 786185904, "item_id": 49136619, "url": "https://news.ycombinator.com/item?id=49136619", "by": "mrinterweb", "date": "2026-08-01", "stance": "recommend", "quote": "This looks fantastic for a common async workflow I use.", "excerpt": "This looks fantastic for a common async workflow I use. I often use one job to fan out multiple individual http request jobs. The reason I prefer jobs for this is easy and consistent retry logic, and durability. I want to make sure those HTTP requests eventually go through. Fibers would be much better suited for this. So much of work that goes onto work queues is IO bound, and fibers are a great fit for that.", "context": "", "use_case": "background job fan-out", "switched_from": "", "story": "Solid Queue 1.6.0 now supports fiber workers"}]}], "caveats": [{"label": "", "summary": "", "quotes": [{"id": 745831585, "item_id": 46614474, "url": "https://news.ycombinator.com/item?id=46614474", "by": "jacob-s-son", "date": "2026-01-14", "stance": "warn", "quote": "They also still have no support for batch jobs", "excerpt": "Every author of the free software obviously has rights to full control of the scope of their project. That being said, I regret that we have switched from good_job (https://github.com/bensheldon/good_job). The thing is - Basecamp is a MySQL shop and their policy is not to accept RDMS engine specific queries. You can see in their issues in Github that they try to stick \"universal\" SQL and are personally mostly concern", "context": "", "use_case": "background jobs", "switched_from": "GoodJob", "story": "I Love You, Redis, but I'm Leaving You for SolidQueue"}]}], "who": [], "tags": [], "use_cases": ["background job fan-out", "postgres-backed job queue", "rails background jobs", "background jobs"], "compared": [{"slug": "redis", "name": "Redis", "co": 2, "switched_from": 1, "switched_to": 0}], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=46614037", "title": "I Love You, Redis, but I'm Leaving You for SolidQueue", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=49132083", "title": "Solid Queue 1.6.0 now supports fiber workers", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49113913", "title": "Postgres Queues Actually Scale", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {}, "2026-01": {"warn": 1, "neutral": 1}, "2026-02": {}, "2026-03": {}, "2026-04": {}, "2026-05": {}, "2026-06": {}, "2026-07": {"neutral": 1}, "2026-08": {"recommend": 1}, "2026-09": {}, "2026-10": {}}, "quotes": [{"id": 786185904, "item_id": 49136619, "url": "https://news.ycombinator.com/item?id=49136619", "by": "mrinterweb", "date": "2026-08-01", "stance": "recommend", "quote": "This looks fantastic for a common async workflow I use.", "excerpt": "This looks fantastic for a common async workflow I use. I often use one job to fan out multiple individual http request jobs. The reason I prefer jobs for this is easy and consistent retry logic, and durability. I want to make sure those HTTP requests eventually go through. Fibers would be much better suited for this. So much of work that goes onto work queues is IO bound, and fibers are a great fit for that.", "context": "", "use_case": "background job fan-out", "switched_from": "", "story": "Solid Queue 1.6.0 now supports fiber workers"}, {"id": 785825248, "item_id": 49114078, "url": "https://news.ycombinator.com/item?id=49114078", "by": "dewey", "date": "2026-07-30", "stance": "neutral", "quote": "even Rails switched to Postgres powered queues by default (SolidQueue) more than 3 years ago", "excerpt": "> The conventional wisdom around Postgres-backed queues is that they don't scale. That might have been the case 10 years ago. In the past years there have been many Postgres powered queueing systems and even Rails switched to Postgres powered queues by default (SolidQueue) more than 3 years ago.", "context": "", "use_case": "Postgres-backed job queue", "switched_from": "", "story": "Postgres Queues Actually Scale"}, {"id": 745846129, "item_id": 46615383, "url": "https://news.ycombinator.com/item?id=46615383", "by": "madethemcry", "date": "2026-01-14", "stance": "neutral", "quote": "while try to integrate SolidQueue myself I found Railway", "excerpt": "DHH also famously describe why and how they are leaving the cloud https://world.hey.com/dhh/why-we-re-leaving-the-cloud-654b47e0 I'm not a fan boy of DHH but I really like his critical thinking about the status quo. I'm not able to leave the cloud or I better phrase it as it's too comfortable right now. I really wanted to leave redis behind me as it's mostly a hidden part of Rails nothing I use directly but often I h", "context": "", "use_case": "Rails background jobs", "switched_from": "Redis", "story": "I Love You, Redis, but I'm Leaving You for SolidQueue"}, {"id": 745831585, "item_id": 46614474, "url": "https://news.ycombinator.com/item?id=46614474", "by": "jacob-s-son", "date": "2026-01-14", "stance": "warn", "quote": "They also still have no support for batch jobs", "excerpt": "Every author of the free software obviously has rights to full control of the scope of their project. That being said, I regret that we have switched from good_job (https://github.com/bensheldon/good_job). The thing is - Basecamp is a MySQL shop and their policy is not to accept RDMS engine specific queries. You can see in their issues in Github that they try to stick \"universal\" SQL and are personally mostly concern", "context": "", "use_case": "background jobs", "switched_from": "GoodJob", "story": "I Love You, Redis, but I'm Leaving You for SolidQueue"}]}