🤖 New Year New.... Heroku?? 👋 (January 2025)
Howdy, Judoscalers! Hope you’re all enjoying the new year and the.. winter. When I looked outside this morning it was a whole 1℉. And it looked just about like this:
So... we hope you’re in a warmer place or perhaps cozied up at home with some hot chocolate! The cold days are upon us 😎. Onward to the Judo tech news! This month we’ve got...
- ⚖️ Scale Your Workers Down To Zero
- 🎉 New Year New.... Heroku??
- 💅 Re-Rendering Render!
- 🧠 Rails on Heroku: How to Use Less Memory
- 📉 Too Many Connections in PostgreSQL?
- 🌶️ Hot Takes on BlueSky
⚖️ Scale Your Workers Down To Zero
...on Render! That’s right: we now support scaling worker processes down to zero instances on Render. We’ve supported this functionality on Heroku for years (and if you’re not using it, you should! It’s free money! 💰) but now have parity feature support for Render, too. Technically, in Render parlance, this is “suspending” your service.. but the idea is the same. Don’t spend money to run instances of a service that aren’t doing anything!
You can read more about that here
New Year New.... Heroku??
We’ve found some exciting breadcrumbs from Heroku’s new platform, set to launch this year. Just a few little docs released quietly here and there for how Fir works in the Private Spaces beta.... but what we’ve seen so far, we really like. Thus, we’ve written an article, Heroku’s New Stack Might Be What We’ve Been Waiting For. Newer, faster dynos; several more dyno resource options; potentially dedicated compute across the board (😱). More to come! Check it out here
Re-Rendering Render!
While our platform integration for autoscaling Render applications has been running smoothly for a couple of years now, we decided to execute some pretty major architectural refactors. Centrally, Render themselves added some organizational features that we wanted to reflect. So now you can sync Projects and Environments from Render over to Judoscale! This allows for much more organic service grouping and organization. We think our Render customers will be super happy with this.
You can read more about this change here
Rails on Heroku: How to Use Less Memory
We released a two-part blog-post series centered on lowering your memory footprint with Rails apps — both in web processes and background workers. We started with some easy, high level stuff (change some ENV vars, tweak some dashboard settings) then dove into some app-level / code changes that might help you out. We’d say it’s definitely worth a read if you’ve ever had memory pressure running Rails on Heroku... but if you’ve run Rails on Heroku, you’ve definitely had memory pressure 😅 so it’s just worth a read through-and-through! Check it out here
Too Many Connections in PostgreSQL?
Adam spent a bit of time writing up this article that pairs with our newly revamped Database Connection Calculator (✨) that will help you understand how to not bork your database by attempting to connect too many things to it! Dynos, Processes, Threads.. oh my! Even if you’re not having any active issues with your database connection counts, the article is worth a trip down reminder-lane and it’s a quick read. Neat!
Hot Takes on BlueSky
Have you recently moved to BlueSky for your tweeting short-form posting? Adam’s on there too, posting hot takes and interesting dev topics every couple of days! Like this one:
This is where we ask the viewer to “like and subscribe”, right? 🤦♂️
That’ll do it for us this month. Hope you all have a swell January and we’ll see you closer to Valentine’s day!
— Jon & The Judoscale Team
P.S.... we've had a bit of an internal debate going lately. We'd love to get your input!