3 ms·
ECS/Fargate and Kubernetes are different, for sure, but it seems like the author is conflating the one-time setup costs of Fargate with the continual maintenanc
by robrtsql 8y ago
ECS/Fargate and Kubernetes are different, for sure, but it seems like the author is conflating the one-time setup costs of Fargate with the continual maintenance costs of running Kubernetes on VMs which you maintain yourself, which doesn't seem like a fair comparison to me.
- jkaplowitz 8y agoHe acknowledges your point in the article but says that most people don't have to administer their own cluster VMs - GKE makes it easiest but he also mentions a smooth experience with DigitalOcean's managed Kubernetes, for example.
- maldeh 8y agoFargate's purpose was never to magically make container orchestration go away, though - it's just a managed compute layer you plug into via the other orchestration frameworks (ECS or EKS). Really the apples-to-apples comparison should be DigitalOcean's managed Kubernetes with EKS (and there are a lot of valid points to raise there, to be sure). The real value-add of Fargate is pay-for-what-you-use, when your task queue is idle and your bill drops to zero with no extra orchestration (something that the article seemingly completely missed).
- YawningAngel 8y agoThe level of orchestration required to achieve this on GKE is pretty minimal.