Top all-time · #4188
Judoscale Dev Blog
Company blog · judoscale.com/blogprogrammingweb
Judoscale Dev Blog is the company blog at judoscale.com, writing about programming and web. Since 2023, 18 different Hacker News readers have linked it 36 times, most often “Heroku's New Stack Might Be What We've Been Waiting For”. It is still writing: the last post was on 2026-10-21, and you can follow it by feed.
A more powerful autoscaler for Heroku, Render, Railway, Fly.io, Scalingo, Northflank, and Amazon ECS. Queue-time scaling for web and workers, with per-process ranges, step size, and schedules.
Most-linked posts?
- Heroku's New Stack Might Be What We've Been Waiting For3 people · 3 mentions · first linked 2025-01-13
- Deciding Between Heroku Alternatives2 people · 2 mentions · first linked 2024-10-07
- The Post-Jamstack Era: Just Use Rails2 people · 2 mentions · first linked 2024-09-13
- Scaling Python task queues is hard2 people · 2 mentions · first linked 2025-05-07
- Your Product Should Be Shiny. Your Stack Should Be Boring2 people · 2 mentions · first linked 2025-04-01
- Dear Heroku: Uhh What's Going On?2 people · 2 mentions · first linked 2026-04-06
- Scaling Sideways: Why You Might Want to Run Two Production Apps2 people · 2 mentions · first linked 2025-11-06
What Hacker News says?
Submitted The Post-Jamstack Era: Just Use Rails as a story · 38 points
HN discussionSubmitted Post-Mortem: How Heroku Router 2.0 Wrecked Our App as a story · 6 points
HN discussionSubmitted Scaling Python task queues is hard as a story · 5 points
HN discussionSubmitted Heroku's New Stack Might Be What We've Been Waiting For as a story · 5 points
HN discussionSubmitted Your Product Should Be Shiny. Your Stack Should Be Boring as a story · 4 points
HN discussionSubmitted Avoiding PaaS Lock-In as a story · 4 points
HN discussionSubmitted Bringing Heroku costs under control as a story · 4 points
HN discussionSubmitted The Post-Jamstack Era: Just Use Rails as a story · 4 points
HN discussionSubmitted Scaling Sideways: Why You Might Want to Run Two Production Apps as a story · 3 points
HN discussionSubmitted Platforms > self-hosting Python apps as a story · 3 points
HN discussionSubmitted Dear Heroku: Uhh What's Going On? as a story · 2 points
HN discussionSubmitted Scaling Sideways: Why You Might Want to Run Two Production Apps as a story · 2 points
HN discussionSubmitted How Judoscale's Utilization-Based Autoscaling Works as a story · 2 points
HN discussionSubmitted Choosing a Python Framework as a story · 2 points
HN discussionSubmitted Scaling Python Task Queues Effectively as a story · 2 points
HN discussionSubmitted Choosing the right Python task queue as a story · 2 points
HN discussionSubmitted The Ultimate Guide to Scaling Sidekiq as a story · 2 points
HN discussionSubmitted Deciding Between Heroku Alternatives as a story · 2 points
HN discussionSubmitted Heroku's New Stack Might Be What We've Been Waiting For as a story · 2 points
HN discussionSubmitted Kamal vs. PaaS – Is it ready? as a story · 2 points
HN discussionSubmitted How ECS Autoscaling Works as a story · 2 points
HN discussionSubmitted How CDNs Work (Propshaft / Static Assets Pt. 2) as a story · 2 points
HN discussionSubmitted Heroku Alternatives as a story · 2 points
HN discussionSubmitted How to Fix Tricky Sidekiq Memory Issues as a story · 2 points
HN discussionSubmitted How Propshaft Works: A Rails Asset-Pipeline (Visual) Breakdown as a story · 2 points
HN discussionSubmitted Hosting a 2,800 RPS app on Render – the good parts and the bad parts as a story · 1 points
HN discussionSubmitted Dear Heroku: Uhh... What’s Going On? as a story · 1 points
HN discussionSubmitted Heroku: What's Next as a story · 1 points
HN discussionSubmitted Hosting Node Apps as a story · 1 points
HN discussionSubmitted BullMQ is usualy the right job queue as a story · 1 points
HN discussion
