4 ms·

All this talk about simplicity but still many AWS services are way more complicated than they should be. Fargate is one example. To just run container, I need a

All this talk about simplicity but still many AWS services are way more complicated than they should be. Fargate is one example. To just run container, I need a ECS cluster, Service, Task Definition, etc. Compare this to Docker-compose. Compare it to Heroku. To make it flexible, it's made very complicated. I know there are tools and CLIs which take this pain away. But even if you deploy it with a tool, you still need to deal with complexity when you want to deal with problems in production.

ignoramous 6y ago
> All this talk about simplicity but still many AWS services are way more complicated than they should be. Agree. It isn't that AWS hasn't gotten anything wrong. There's plenty services languishing in mediocrity or worse (Ever see anyone recommend Flexible Payment Service over Stripe, or CloudFormation over Terraform?) For services that are popular, it so happens that AWS favours iteration: There's always a tension between what to leave out and what to build, but as Werner explains, AWS prefers its customers drive the roadmap rather than having to invent everything all at once which makes it too difficult to later change course (see: SimpleDB vs DynamoDB) in an industry that changes very fast. Also, simple and easy don't quite mean the same things :) but I get your gripe. That's why I believe platforms like Cloudflare Workers, Firebase, Heroku, Fly.io, StackPath EdgeEngine will thrive despite the existence of larger cloud providers.