I pretty strongly agree. Fargate is a great product, though it isn't quite perfect.
ECS is far, far far smoother, simpler and stable than anything else out there in cluster orchestration. It just works. Even with EC2 instances it just works. And if you opt for Fargate, then that's far more stable option.
I am saying this after bootstrapping k8s and ECS both.
The only pain point there I think is auto scaling logic. But otherwise it’s painless.
I find auto-scaling with fargate to be pretty straightforward. What's the pain point there for you?
It works, but the way it’s not part of fargate, and instead some combination of cloudwatch events and rules modifying the ‘desiredCount’ property on the service.
Just feel like it could all be done in a slightly more integrated way.
GCP Cloud Run is even better, which you don't have to configure those networking stuff, just ship and run in production
Does Cloud Run give you a private network? While configuring it is annoying, I do want one for anything serious.
How does it compare with fly.io? Last I checked, startup time is still in minutes instead of less than a second on fly, but I presume it's more reliable and you get that "nobody ever got fired for using AWS" effect
Fly.io is an unreliable piece of shit.
Fly is really cool and it's definitely an extremely quick way to get a container running in the cloud. I haven't used it in production so I can't speak to reliability, but for me the main thing that stops me from seriously considering it is the lack of an RDS equivalent that runs behind the firewall.
Re:Reclaim the Stack
by hannofcart on Monday September 09, 2024 @10:39AM
(#41488966)
+1 on this. ECS Fargate is great.
I’ve used kubernetes as well in the past and it certainly can do the job, but ECS is my go-to currently for a new project. Kubernetes may be better for more complex scenarios, but for a new project or startup I think having a need for kubernetes vs. something simpler like ECS would tend to indicate questionable architecture choices.