Amazon ECS Autoscaling Without an Ops Team
queue time, ranges, and schedules for web services and workers.
“The first step to a scalable web service is automatic autoscaling. Without autoscaling, you're just waiting for a flash sale, social media post, or other "white swan" event to take down your site at just the wrong moment. ”
Engineered for your stack
Judoscale has custom libraries built specifically for Ruby, Python, Node.js, and Java. Each library integrates with popular web frameworks like Rails, Django, Express, Next.js, and Spring Boot, as well as job backends like Sidekiq, Celery, and BullMQ—so you get accurate metrics without manual configuration.
Queue time, without the metric pipeline
Queue time is the true measure of task capacity. Judoscale collects it and scales your web services and workers on it, without a custom CloudWatch metric pipeline to build or maintain.
Learn more about request queue time →The controls, without an ops team
Set the range, how many tasks to add or remove per scale event, and how often Judoscale scales up and down. Each service is independent, and you can add a schedule when traffic is predictable.
Web services and background tasks
Queue time isn’t just for web services. Judoscale also uses queue latency to autoscale your background tasks, ensuring your job queues never back up.
Faster and more reliable than Amazon ECS’s autoscaler
A capacity issue needs to trigger autoscaling as quickly as possible, and Judoscale is the fastest autoscaler available. Our autoscaling algorithm runs every 10 seconds, ensuring your app scales up before users notice an issue.
Reduce your Amazon ECS compute costs
Your ECS tasks are probably overscaled, and Judoscale can help. Our autoscaling algorithm is more efficient than ECS’s, allowing you to scale down without sacrificing performance or peace of mind.
- Trusted by900+engineering teams
- Over2.5 millionrequests per month
- Since2017we are here to stay
Still have questions?
Check out our docs for a whole lot more. If you still can’t find what you’re looking for, send us an email!
What languages and frameworks does Judoscale support?
We support many web frameworks and job/task queues for Ruby, Python, NodeJS, and Java. See the full list in our docs.
What data can Judoscale access in my app?
Our language-specific packages only collect queue-related metrics for requests and job queues along with basic process metadata. No actual request or job data is ever collected.
Can we have a call to see if Judoscale makes sense for my app?
Sure, let’s talk! Use this link to book a call with us.
You guys are rock stars!! I think this is the 3rd time now that you've already had a solution ready to go to solve our problem. This is exactly what I was looking for!!
If I was the king of the world, I would make it illegal to horizontally scale based on execution time. Scale based on queue depths, people!
Judoscale’s deep integration with Sidekiq queues let us easily tag which queues we wanted a faster response. We were able to tune our scaling sensitivity for exactly our usage pattern of intermittent batches of large jobs.
Chameleon has been extremely stable thanks to Judoscale. We have very high spikes in traffic, and I don’t even have to think about it.
Request queue time is the single most important part of this. Scaling by CPU and memory consumption makes no sense—your server should have stable memory usage and nearly 100% CPU utilization.
Our servers now happily scale anywhere from 2 to 15 dynos, saving us thousands a month.
Judoscale has been really easy to configure, and it just works — unlike others autoscalers we’ve tried. It delivers consistent, expected scale patterns without ongoing attention from us.
Start autoscaling for free
Setup takes less than 5 minutes