Hacker News Reader

I think the problem went deeper than that actually. Mesos required that applications use a distributed system API to interface with the executors. This meant it was very challenging to write a distributed system upon Mesos, even though that was ostensibly the very thing that Mesos was meant to solve. When K8s came along and made everything manifest and YAML-based, we sort of knew that we were screwed because of how much simpler that was.

View on HN

Eh, maybe. I see your point.

The thing is, Mesos on it's own isn't k8s. Mesos is a scheduler. k8s is a full stack. So it's always been a bit off to fully compare the two.

If your system fit clearly within what k8s did well, then you were fine and the stack worked.

If you had a more complicated architecture with parts that didn't play well with containers or k8s' scheduling model, life became pretty difficult.

That's one reason I liked Mesos is you could build the stack you needed for _your_ infrastructure.

Granted, I don't think most shops had the kind of problems that warranted Mesos, let alone k8s (that's still true today). But k8s is "good enough" for lots of problems and understandably that's where the community went.

Reply on news.ycombinator.com