Hacker News Reader

If I understand this correctly, Fargate is similar to Elastic Container Service, without having to worry about EC2's instances? But you also can manage the EC2 instances with Fargate as well? Seems like AWS has lots of products that overlap and it is confusing to end users.

I'd say this is exactly why Google Cloud is superior (in my opinion). AWS lacks user experience and KISS philosophy. Just feels like AWS keeps on bolting things on.

View on HN

Actually I think their approach is great—it's very modular and there's little overlap between use-cases. An exception (among a few) may be ECS and EKS, where ECS was probably the wrong bet for them now that K8s is getting so much traction. Hence EKS.

But being able to put use either EKS or ECS for orchestration, and then schedule those tasks on either EC2 or Fargate (depending on compute needs), opens up a lot of options. You can start simple and grow as requirements become more complex—without fundamentally changing the deployment artifact. That was the promise of containers originally, so it's nice to see it play out.

No, Fargate is just a container target, like EC2 is.

You manage the containers with ECS (Or the newly announced Kubernetes equivalent). They are placed on either EC2 instances or somewhere inside Fargate.

Reply on news.ycombinator.com