The Judoscale Newsletter logo

The Judoscale Newsletter

Subscribe
Archives
September 20, 2024

🤖 Judoscale News: Autoscale and Chill? 👀 (September 2024)

Greetings Judoscalers 👋!

It’s time again for another issue of Judoscale News! And we’ve got quite a bit to cover — so much so that we’re going to start including a handy little table-of-contents here for you. Let’s dive in!

  • 🆕The Ninja Has a Name!
  • 🛠️ Log Them Changes
  • 📝 The Post-JAMstack Era...
  • 🎥 Adam on the Big Screen
  • 📝 Say No to Partials and Helpers?
  • 📝...How Bad Can it Get??
  • 📝 Rails’ Puma Config Change
  • 👀 Autoscale and Chill

 

🆕 The Ninja Has a Name!

We solicited input from all of you (thank you!) on what we should name our little ninja friend that’s part of our new branding:

The new Judoscale logo with the Judoscale ninja to the left of the name

And we finally have a name! Otto, the Autoscaling Ninja. A fun little play on words (“Otto” == “Auto”) and a great suggestion from a friend of Judoscale. Just remember, Otto’s always watching...

...your autoscaling 😉

 

🛠️ Log Them Changes

We’re excited to show off that Judoscale now has an official(™️) changelog system. While we’ll definitely still be talking about features and things here in this newsletter, if you’re interested in finer-grain details, we’d recommend you check it out! We consider it our source-of-truth for platform changes over time from here on out.

You can find it at changelog.judoscale.com:

A screenshot of the new changeling system featuring our latest update

In addition, since we’re using Headway (highly recommend!), we also have a convenient little widget that will display in Judoscale’s own dashboard. You’ll find it un-annoyingly at the bottom right corner of the window, ready to inform you about any new changes we’ve released:

A screenshot of the Judoscale dashboard showing the change log widget at the bottom

 

📝 The Post-JAMstack Era...

We released a spicy new article this week! And it’s been received with more positive energy than we thought it might be, honestly. We’re not usually a team of hot-take folks, and maybe it’s less of a hot take since most of the readers are already Rails developers, but nonetheless! We think you’ll enjoy giving this a read and letting go of some old mindsets 😁

Check it out here:

The share-image for the article; just a title on a green background

And also...

 

🎥 Adam on the Big Screen

While the Post-JAMstack article above covers a lot of the why behind the switch, Adam recorded and released a video covering a ton of the how! Given that our previous site was built on NextJS — broken down into hundreds of little React components and Javascript bits — seamlessly converting all of that into Rails without breaking our styling was a real challenge. Adam to the rescue!

Give it a watch on Youtube here:

A thumbnail of Adam and the video title

 

📝 Say No to Partials and Helpers?

While we’re on a roll with hot-takes, how about running a Rails app and not using view partials or helper modules at all? If that feels like a wild suggestion or uncomfortable for you (and believe me, it still does for me), then this article is for you! We’ve been on the Phlex train for a little while now and Adam wanted to take a stand for how it can really help app organization. It’s more than a template system; it’s an organization boon.

Learn more right here:

The share-image for the article; just a title on a green background

 

📝 ...How Bad Can it Get??

...with shared hardware, that is! There’s been some chatter in the quiet corners of the Heroku performance world the last few months. Between some eyebrow-raising implications made by Heroku itself and some of our continued research, we’re discovering some really interesting findings with Heroku’s shared-hardware options (e.g. Standard-1x and Standard-2x). If that sounds vague, it’s because a lot of it is! But we do have some specifics to say.

Find out how bad it can get here:

The share-image for the article; just a title on a green background

 

📝 Rails’ Puma Config Change

We wanted to share one more article with you all this month: a discussion around why Rails changed the default Puma config and how that impacts Puma’s operations in the first place. Trying to talk through the impacts of multi-threading in a web-server context is tricky, so we took a visualization-heavy approach to try to make it clearer to understand.

Give it a look right here:

A screenshot from the article showing a few of the visualizations used along the way

 

That’ll do it for this month’s edition! Plenty of interesting topics fresh off the presses. We hope you all have a great rest of your September and enjoy the leaves beginning to change (in the Midwest USA, at least)! Can you believe we’re already 75% of the way through 2024??

Cheers!

— Jon & The Judoscale Team


 

P.S. Autoscale and Chill!?

Rails world is next week! Carlos and Adam will be there, both excited to meet all of you! We’ll be repping our new T-shirts, carrying our new favorite moniker: Autoscale and Chill. (And yes, I (Jon) forced Adam into this posed shot 😂):

Adam wearing the new ‘autoscale and chill’ shirt while laying sideways on a wall

Is it a play on a common meme about a certain video streaming service? Yes! Is it also true that when you autoscale your life is more chill? Yes!

A straight-on picture of Adam wearing the new shirt to better see the design

So if you see us at Rails World, say hello! We might just have a few shirts to give away to those that would also like to Autoscale and Chill — no funny poses required 😏. And, I can confirm, they are quite comfy 😌

 

Don't miss what's next. Subscribe to The Judoscale Newsletter:
Website X
This email brought to you by Buttondown, the easiest way to start and grow your newsletter.