3 ms·
But it's never just ECS/Fargate is it. It's ECR, S3, ALB, CF etc. And at that point you've assembled a stack just as complex as doing it all inside a single k8
by threeseed 2y ago
But it's never just ECS/Fargate is it. It's ECR, S3, ALB, CF etc.
And at that point you've assembled a stack just as complex as doing it all inside a single k8s cluster.
- sverhagen 2y agoHence I said "I personally" and "already have familiar tools". Also, if you're fair... not all those AWS acronyms you're listing would be displaced by the single k8s cluster. (Maybe you weren't arguing to swap out complexity, rather that the complexity floodgates were open already anyway?)
- threeseed 2y agoYou can absolutely run object store, container serving, front end load balancing etc from a single k8s cluster. Very common in fact since many k8s clusters are air-gapped except for a single inbound edge node.
- ghomem 2y agoAnd if one of those services is down, your entire application is down. You basically build a server made of abstract components ECR, S3, ALB, CF , all of which are able to fail.
- kidros 2y agoExcept it's not anywhere near as complex because you need to manage far far less using the AWS services than if you ran all of your own inside a k8s cluster. And even if you use k8s, you're probably already using most of those anyway. Who bothers building their own container hosting and file hosting at a startup?