3 ms·
I'm in exactly the same boat as you with the caveat that I did look into and test DC/OS. It is too little too late. Also I see Mesosphere (as a company) more or
by SEJeff 10y ago
I'm in exactly the same boat as you with the caveat that I did look into and test DC/OS. It is too little too late. Also I see Mesosphere (as a company) more or less smothering the ecosystem very similarly to how Docker is doing with Swarm and the Docker ecosystem.
I went to MesosCon this year and the previous. Last year it was a really fun kind of scrappy conference. This year it was basically "buy DC/OS". Even the open source vendor booths all had "works with DC/OS" stickers. It reminded me of "Dell recommends Microsoft Windows XP Professional for the best experience" crap that Microsoft used to pull with OEM's licensing windows. I was really unimpressed. Whereas Mesosphere is adding hooks into mesos to add things like AAA (Authentication, Auditing, Authorization) and then implementing it as proprietary modules in their commercial DC/OS, It is native and open source in Kubernetes (thanks to Redhat contributing code from openshift).
So on one hand I see a young ecosystem being swallowed by a single vendor who is slowly squashing the community. On the other hand I see several vendors doing everything in the open and a huge community. With the technical capabilities of both quickly converging as k8s implements a lot of the things Mesos used to have over it, Mesos is becoming less and less "sexy" and more like a liability unless you want to roll your own everything like Apple did with their Jarvis scheduler for Siri.