🤖 Judoscale News: On a New Schedule(r) 📆 (August 2024)
Autoscale and Chill?
Greetings, Judoscalers! We’re excited for this latest edition of the Judoscale News — there’s a lot to cover! New features, behind-the-scenes details, and new releases!
Judoscale’s New Scheduler
If you run any kind of schedule for your applications on Judoscale (and you probably do), we’re excited to show you this preview of our new scheduling interface! We shared a brief image preview of some new calendar-style concepts last month, but the rebuild has since been implemented and is now in beta! While we continue to iterate on the UI and make subtle tweaks to improve it, we expect it to launch for all customers soon. If you can’t wait and want to be part of our beta, let us know!
Making the Sausage: The Scheduler
In addition to offering our new autoscaling-scheduling UI soon, Adam took some time to record a video explaining how it’s built! The new UI is built with Turbo Frames, Phlex, Tailwind, and a touch of Alpine.js, and Adam walks through the entire build process for how each of those components works together. Definitely worth a watch if you’re interested in any of those tools, or just want to see how your favorite autoscaling tool works under the hood 😁
Maintenance Mode is Here!
We’ve gotten several requests over the years for a feature that would shut off autoscaling for an entire app at once, temporarily. We’ve taken to calling this simply, ‘Maintenance Mode’, and we’re excited to announce that it’s now available! Maintenance mode will automatically scale worker processes down and prevent any autoscaling on web processes — exactly what most applications need at those times. Read more about that here.
DIY-Scale
Don’t worry, we won’t be offended if you read this article 😉. Kidding aside, over the years we’ve had lots of folks ask for platforms, frameworks, and other setups that we don’t (yet?) support. And, even if we do support their setup, not everyone wants an easy, out-of-the-box autoscaler! For those reasons, and to explain a little bit of the complexity required for our big autoscaling machine to work, we wrote an article about the layers and safeties involved in building your own autoscaler. Even if you don’t ever plan to run your own custom autoscaler, this is a great read to better understand what we do to ensure our data is consistent and accurate 24/7/265:
Sidekiq Iterable What?
Did you see that Sidekiq released a big new feature in v7.3? Indeed, we now have Sidekiq ‘Iterable Jobs’, and they represent an interesting new promise / workflow in the Sidekiq world! Interested? Check out this article where we explored when to, and when not to, reach for this great new tool in our tool-belt:
Sidekiq Iterable... Forever-Jobs?
Shortly after publishing the article above, we realized we could utilize the Sidekiq Iterable Jobs feature to accomplish something we’d written about before: safely repeating work in a single-threaded manner infinitely! We even have a whole blog post about it. Turns out that running an Iterable Job with an infinite list actually accomplishes the same goal while letting Sidekiq itself handle most of the responsibility and execution guarantees. This is a neat extension! Check it out here:
And that’ll wrap up the August edition of the Judoscale News! Hope you all have a wonderful month and we’ll see you on the other side — the precipice of Fall; September 🍂. Time sure has flown by this year...
Cheers!
— Jon & The Judoscale Team
P.S. Will we see you at Rails World? The Judoscale team will be there and would love to meet you, talk shop, give you a T-shirt, and otherwise enjoy Toronto with you! Let us know if you’ll be around; we love spending time with our community ❤️