> It's not clear to me that K8s was the actual thing that helped them scale, but rather the work they put into reworking their services. It seems you're missin

> It's not clear to me that K8s was the actual thing that helped them scale, but rather the work they put into reworking their services. It seems you're missing the forest for the trees. They put in the work to refactorize their services so that they could be treated as cattle and also autoscale, and the author stated that after doing his homework he determined that for his company Kubernetes offered the most benefits. There isn't much to read from this. > Just to add on my point, wouldn't the result (in terms of performance / resources usage) be the same if instead of "containers" the author had chosen "AMIs" and instead of "Kubernetes" the author had opted for "Autoscale Groups"? The author explains that he considered using EC2 instances but after analising the tradeoffs the company decided to just jump to EKS. If you'd like to debate containers vs VMs then it's perfectly fine, but the author of this blog post just documented his learning path and pointed out what worked for him. Sometimes you need to call a shot, and the tradeoffs you need to consider are so minor and irrelevant that a coin flip will do.