5 ms·
One more thing Since I have set-up both in production (and more than once) I can tell you for a fact. Kube is easier to setup and easier to run with less probl
by avitzurel 10y ago
One more thing
Since I have set-up both in production (and more than once) I can tell you for a fact. Kube is easier to setup and easier to run with less problems along the way.
Since I am running essentially the same cluster on kube that I ran on mesos, this is a no-bullshit comparison.
[To be fair]
I never used dc/os, I used marathon and chronos on top of mesos.
- amr_abdelrazik 10y agoYou should give DC/OS a try, Mesos required some time and skill to implement, DC/OS GUI and CLI installers solves that completely.
- avitzurel 10y agoI absolutely agree. DC/OS looks really interesting. I am working on an open source project called "The Startup Stack" to essentially help startups bootstrap (and manage) a cluster in the cloud. link: http://docs.the-startup-stack.com/ http://docs.the-startup-stack.com/ Right now, it's working using mesos/marathon etc... 2 companies are using it in production. In the last couple of months I've been thinking about making the move to Kube for this project. I might evaluate DC/OS as part of it. Working on this project made me appreciate how hard it is to generalize and hit everyone's taste. There's a lot of customizing around cloud infrastructure now and I definitely feel there are more common grounds we can create. I'll give DC/OS a shot before making my final decision. Thank you for your suggestion and your awesome comments on this thread. I was always impressed with the mesosphere team in previous discussions here on HN.
- avitzurel 10y agob.t.w, when I started the-startup-stack DC/OS was an enterprise offering. Coincidentally, you announced the open source version on my birthday this year. Maybe it's a sign :)
- amr_abdelrazik 10y agoyou are welcome, and if you need anything just reach out on the dcos slack community channel, you can find me there
- SEJeff 10y agoI'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.