AWS ECS auto-scaler is broken
(don’t worry, we’ve fixed it)
If you run Node.js services on AWS ECS, you don’t have many built-in ways to handle changing loads. Your only two options respond within minutes: Target Tracking Scaling and Step Scaling. Both monitor
blog.platformatic.dev25 min read
This is a really insightful comparison! The distinction you draw between AWS ECS's traditional autoscaling (which reacts to metrics) and Platformatic ICC's predictive/intelligent approach is super clear.
What stood out to me the most:
The latency argument: Waiting for CloudWatch metrics + ECS to react means your app already feels slow to users. ICC's proactive scaling actually makes sense for real-world user experience.
Cost transparency: Breaking down the hidden costs of over-provisioning vs. under-provisioning is something most comparisons skip.
I'm curious though — for smaller startups or side projects where traffic is unpredictable but not necessarily high-volume, would ICC still be cost-effective? Or does the sweet spot come at a certain scale threshold?
Also, the platformatic upgrade command being that simple is tempting 😄 Has anyone tried migrating an existing ECS service to ICC in production? Would love to hear war stories if so.
Great write-up, definitely making me rethink my infrastructure choices!