News for hackers. Stuff that matters.
Re:Container orchestration: Moving from fleet to Kubernetes by davidmr on Tuesday February 07, 2017 @11:40PM (#13595810)
Completely agreed. The landscape 2-3 years ago looked incredibly different, and I picked Mesos for a rather ambitious project. After it became relatively clear that k8s was going to eclipse Mesos and not by a little bit, trying to unwind that decision basically cost me my job through some political infighting. It's a shame, but such is the price of early adoption, I guess.

Given the same information, I'm really confident that I'd still make both choices the same way.

Re:Container orchestration: Moving from fleet to Kubernetes by wmf on Wednesday February 08, 2017 @12:53AM (#13596134)
It could have been worse: You could have tried to run Swarm and k8s on top of Mesos simultaneously.
Re:Container orchestration: Moving from fleet to Kubernetes by benjamin_mahler on Wednesday February 08, 2017 @03:03PM (#13601516)
Hi David, can you reveal some of your environment (e.g. on-prem vs cloud), were there any technical reasons for switching or was it primarily a matter of perception of velocity/popularity between the two projects?

Just to add some of my own perception as someone who works on Mesos, Mesos continues to be popular with large technology companies that don't make their technical investments lightly: Twitter, Apple, Netflix, Uber, Yelp, for example. Companies continue to choose a Mesos stack based on its technical merits. The project is still moving fast and adding powerful primitives to support the needs of production environments while distributions like DC/OS are trying to make Mesos more approachable (easy to install, administer) and comprehensive (providing solutions for load balancing, logging, metrics, etc). I hope you will take another look at the Mesos ecosystem at some point, a lot of care has gone into it :)

Re:Container orchestration: Moving from fleet to Kubernetes by mentat on Wednesday February 08, 2017 @04:54PM (#13602522)
Not OP, but I think the perception is that Mesos requires you to roll a lot more of the solution yourself. That's fine if you're a large company who can throw hundreds of developers at your platform, less so if you've got 5 or even 50.