1 day ago · Tech · 0 comments

Every few months I have the same conversation. A small team, three to eight engineers, is containerizing their app, and someone says “we should use Kubernetes, that’s the industry standard.” Six months later they’re maintaining a small distributed systems platform on the side, and the app they were supposed to ship is still competing for attention with CNI upgrades. I’ve written before about the ECS decisions that waste six weeks. This post is the prequel: what ECS actually is, how it maps onto the Kubernetes concepts you already know, and what you stop carrying on your pager when you choose it. There are a few interactive diagrams below. Click around in them; they teach the model faster than prose does. One thing before we start: this is not a “Kubernetes bad” post. EKS is the right choice for some teams, and I’ll tell you exactly which ones at the end. But I’ve watched too many three-person teams default to EKS because it felt like the serious choice, without anyone explaining what…

No comments yet. Log in to reply on the Fediverse. Comments will appear here.