Judoscale: One-Click Autoscaling for any hosting platform ✨

Greetings, Judoscalers! Hope you’re all enjoying the beginnings of Fall (here in the northern hemisphere, at least) and seeing positive traffic in your applications! The cooler fall weather has been a welcome contrast to the humid summer we’ve had here in Ohio. Bring on the colors! 🍁🍂

We’ve got some neat articles and features lined up for you this time around:

• 📝 What Nearly a Decade of Autoscaling Your Apps Has Revealed to Us
• ✅ Judoscale + Terraform = Amazon ECS Joy
• 📝 Where to Host a Python Web App
• 📝 An Outage Explained
• 🎙️ Adam on the Mic!
• 📝 How to Choose a Node.js Framework

Let’s dive in!

📝 What Nearly a Decade of Autoscaling Your Apps Has Revealed to Us

Our little team is extremely proud to be inching closer to that ten-year mark — autoscaling millions of times along the way! We put our heads together and thought about some interesting insights that we could give back after so many years staring at a single concept... and we feel like we’ve got some good points to share. Highly recommended reading for all devs! Read here:

✅ Judoscale + Terraform = Amazon ECS Joy

We’re excited to announce that we’ve further expanded our AWS support, this time in terms of developer ergonomics: Judoscale now works seamlessly with Amazon ECS applications that want to Terraform their way into autoscaling! That is, Judoscale can be easily configured to work with Terraform-based setups and runs right out of the box — just copy the code we generate for you, read it (of course), then run terraform apply! Adam even recorded a video walkthrough for our docs, here:

📝 Where to Host a Python Web App

As we approach Q4 2025, the number of options for where to host an application has only continued to grow. What is Docker? Where’s Amazon? How do you pronounce Heroku? Who is Hetzner? All valid questions. We’ve got some thoughts! And luckily, even if you’re not a Python user/developer, most of these insights apply to every web application back-end. Find out where you should host here:

📝 An Outage Explained

Several weeks ago Judoscale’s autoscaling service had an outage. For most of the night-time (according to Eastern standard time) we weren’t actually executing autoscales for our client applications. The good news? Most applications didn’t seem to have trouble — USA overnights tend to be our least-scaling periods. The bad news? That’s still an outage! The redeeming quality? Adam wrote up an extremely transparent post-mortem that was tough to put out there, but which we think is what we’d want to see and read if we were developers left hanging on the other end. So, in the name of even more transparency, we’re sharing that here in our newsletter. Please read the full article here:

🎙️ Adam on the Mic!

On a more exciting note from this last month, Adam was a featured guest on the Ruby Gems Podcast! Ranging from Adam’s background and life before Judoscale to the origin story of Judoscale itself, this 38-minute episode proved to be a bit of a technical discussion, a bit of bootstrapped-business-evangelism, and possibly even some gluten-filled corollaries! Check it out here:

📝 How to Choose a Node.js Framework

Okay, hear us out. We know there are a million javascript frameworks out there. We know a typical node_modules directory is several, several megabytes. We know that Deno is just splitting things up more!! Drama!

But take a step back for a moment. If you’re in the position of needing to spin up a new application and you’re planning on using Javascript, you actually do need to figure out which of a zillion libraries and frameworks to choose. That’s exactly the question we sought to answer in this one — with some thoughtful questions to guide us along the way. Give it a read here:

That’ll close out the Judoscale News for September, folks! From our little team of 2.5 to yours, we hope you have a wonderful Fall ahead, great success with your applications, and lovely weather abounding 😁. Stay scaled!!

— Jon & The Judoscale Team