What are the key takeaways from this The Bike Shed episode?

Key insights include: **SLA-Based Queue Naming:** Name queues by completion time requirements like "within-5-seconds" or "within-5-minutes" rather than vague names like "high" or "urgent". This creates clear business decisions about job placement and enables precise autoscaling thresholds based on actual service requirements.; **Queue Latency Over Depth:** Monitor how long the oldest job has waited in queue rather than total job count. Latency directly maps to SLA compliance, while depth numbers lack context—a thousand jobs might process in one second or take many minutes depending on job complexity.; **Three Queue Architecture:** Start with three SLA-based queues (five seconds, five minutes, five hours) to handle most use cases. Isolate each queue to separate worker processes for simpler bottleneck identification, independent resource tuning, and the ability to scale memory-intensive queues independently.

What did Adam Mccrea discuss on The Bike Shed?

Adam McCrea, founder of JudoScale, explains queue optimization strategies for web applications, including SLA-based queue naming, job shape analysis, memory management, and autoscaling approaches that improve performance while reducing infrastructure costs. Key topics include: **SLA-Based Queue Naming:** Name queues by completion time requirements like "within-5-seconds" or "within-5-minutes" rather than vague names like "high" or "urgent". This creates clear business decisions about job placement and enables precise autoscaling thresholds based on actual service requirements.; **Queue Latency Over Depth:** Monitor how long the oldest job has waited in queue rather than total job count. Latency directly maps to SLA compliance, while depth numbers lack context—a thousand jobs might process in one second or take many minutes depending on job complexity..

How long is this episode of The Bike Shed?

This episode is 40 minutes long. SignalCast provides an AI-generated summary so you can get the key insights in about 3 minutes.

The Bike Shed

470: All about queues with Adam McCrea

August 19, 2025

40 min episode · 2 min read

Adam Mccrea

Episode

40 min

Read time

2 min

Topics

Startups, Leadership, Software Development

AI-Generated Summary

Published Dec 25, 2025

Key Takeaways

✓SLA-Based Queue Naming: Name queues by completion time requirements like "within-5-seconds" or "within-5-minutes" rather than vague names like "high" or "urgent". This creates clear business decisions about job placement and enables precise autoscaling thresholds based on actual service requirements.
✓Queue Latency Over Depth: Monitor how long the oldest job has waited in queue rather than total job count. Latency directly maps to SLA compliance, while depth numbers lack context—a thousand jobs might process in one second or take many minutes depending on job complexity.
✓Three Queue Architecture: Start with three SLA-based queues (five seconds, five minutes, five hours) to handle most use cases. Isolate each queue to separate worker processes for simpler bottleneck identification, independent resource tuning, and the ability to scale memory-intensive queues independently.
✓Memory-Intensive Job Isolation: Quarantine high-memory jobs to dedicated queues with expensive hardware that scales to zero when idle. This prevents a single memory-heavy job from forcing all workers onto costly performance instances, reducing infrastructure costs by 80% in typical scenarios.

What It Covers

Adam McCrea, founder of JudoScale, explains queue optimization strategies for web applications, including SLA-based queue naming, job shape analysis, memory management, and autoscaling approaches that improve performance while reducing infrastructure costs.

Key Questions Answered

•SLA-Based Queue Naming: Name queues by completion time requirements like "within-5-seconds" or "within-5-minutes" rather than vague names like "high" or "urgent". This creates clear business decisions about job placement and enables precise autoscaling thresholds based on actual service requirements.
•Queue Latency Over Depth: Monitor how long the oldest job has waited in queue rather than total job count. Latency directly maps to SLA compliance, while depth numbers lack context—a thousand jobs might process in one second or take many minutes depending on job complexity.
•Three Queue Architecture: Start with three SLA-based queues (five seconds, five minutes, five hours) to handle most use cases. Isolate each queue to separate worker processes for simpler bottleneck identification, independent resource tuning, and the ability to scale memory-intensive queues independently.
•Memory-Intensive Job Isolation: Quarantine high-memory jobs to dedicated queues with expensive hardware that scales to zero when idle. This prevents a single memory-heavy job from forcing all workers onto costly performance instances, reducing infrastructure costs by 80% in typical scenarios.

Notable Moment

JudoScale experienced its worst outage in nine years when unexpected future-timestamped metrics from one customer broke autoscaling for all customers. The team published a detailed postmortem explaining how data isolation failures affected their entire platform, demonstrating transparency in crisis management.

Know someone who'd find this useful?

Episode Transcript

Auto scaling is a simple concept. Automatically add resources when needed and automatically shut them down to avoid paying for excess capacity. How hard could that be? If you've set up auto scaling yourself, you know it's not that easy, especially using the native auto scalers on platforms like AWS and Heroku. That's why you need Judo Scale. Judo Scale is auto scaling as a service, and they make auto scaling simple and easy, as it should be. You can use Judo Scale on AWS, Heroku, Render, fly.io, and more. It's free for low traffic apps and unlimited plans start at $25 per month. Autoscale on easy mode at judoscale.com. Hello, and welcome to another episode of the Bike Shed, a weekly podcast from your friends at Thoughtbot about developing great software. I'm Joelle Kenville. And today, I'm joined by Adam McRae, the founder of JudoScale. Hey, Joelle. Thanks for having me. And together, we're here to share a bit of what we've learned along the way. So, Adam, what's new in your world? A couple things come to mind right away. So the most significant thing that's new in my world is that yesterday, we had the worst production outage we've ever had in the nine year history of Judo scale. And I'm happy to talk about that more. But to start on a more fun note, the other thing that's new in my world is we're having a garage sale. I don't know if that's a a universal thing or if that's an American thing or not, but, basically, we take all the crap in our house that we don't want anymore. We put it in our garage and try to sell it to people as they as they come by. And it's my two daughters who are 18 and 20 years old who decided to do this. They're owning the whole thing. They had a bunch of stuff they wanted to get rid of. And so, yeah, it's been super fun just, like, watching them work together on this thing and have fun. And we haven't had a garage sale in, you know, probably fifteen years or something like that. And it's not something I ever thought I would do again, but they're running it. So it's great. The joy of, delegation. Yeah. Absolutely. And, you know, they they call me in for help now and then. But, yeah, for the most part, they're owning the whole thing and having a lot of fun doing it, so it's cool to watch. Do you, like, put out signs in the neighborhood or anything like that? They did. They did. That was that was all them. They put a bunch of signs on. I don't even I don't even know where all they put signs, but they left the house with a lot of signs. And, yeah, we've we've had good traffic today. It's, actually, it's wrapping up just now as we record this, but, today so today's Friday, …

Get the full transcript (7,582 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all The Bike Shed transcripts →