5 ms·

What is the benefit of using Kubernetes over Mesos (or in conjunction with Mesos)?

by asimpletune 9y ago

gtaylor 9y ago
The answer to that depends on your particular usage case and requirements. There is no simple, always-true response.
- asimpletune 9y ago
  What are some examples of each?
whalesalad 9y ago
I cannot think of a single reason to choose Mesos over Kubernetes unless you are literally Twitter.
vicaya 9y ago
FTFA: "We’d previously been using Chronos (with Mesos) as a cron job scheduling system, but it was no longer meeting our reliability requirements and it’s mostly unmaintained (1 commit in the last 9 months, and the last time a pull request was merged was March 2016) Because Chronos is unmaintained, we decided it wasn’t worth continuing to invest in improving our existing cluster." Though Chronos has a release recently with a bunch of fixes, Mesos is inevitably fading as a legacy platform.
- asimpletune 9y ago
  > Mesos is inevitably fading as a legacy platform. Because of Chronos? This is a bizarre thing to say. Mesos actually works extremely well. Whenever I ask the why kube over Mesos question, I never get a good answer. I think because people just don’t know Mesos. Also it wasn’t made by google.
  - vicaya 9y ago
    Chronos is just an example. There're many bugs in Mesos that don't get fixed for months/years. Mesos core is legacy (pre 11) C++ code nobody wants to maintain.
    - pm90 9y ago
      > Mesos core is legacy (pre 11) C++ code nobody wants to maintain. This is actually very very VERY important. Go is a lot more concise (IMO) that C++, generally when I'm curious about how something works in a project written in Go, its much easier to follow the logic.
      - asimpletune 9y ago
        Go is nice. I like it a lot. It's very readable, it reduces the number of good ways you can do something to usually just one, it's fast, fat binaries are awesome, great concurrency primitives, etc...
      - benjamin_mahler 9y ago
        There's something to be said about how the code is written. I've seen easy to read C++ and hard to read go (I found go's built in http server source code to be a tough read) and vice versa. In Mesos we strive to write very readable code and so I would hope that despite being modern C++, it is approachable for an uninitiated reader.
    - asimpletune 9y ago
      This whole thread reads like it's from n-gate.
    - hatred 9y ago
      Please don’t spread FUD when you have no clue what you are talking about. Mesos core is certainly not legacy and has been on C++11 for a long time/is very well maintained and has a large active development community. In case a bug has fell through the cracks; kindly reach out on the user mailing list and I am reasonably confident you would get a response. Disclaimer: Apache Mesos committer/PMC
- benjamin_mahler 9y ago
  Take a look at the Mesos releases, a lot of progress is being made and and the project is well maintained. Where are you getting this misinformation?

What is the benefit of using Kubernetes over Mesos (or in conjunction with Mesos)?

gtaylor 9y ago

The answer to that depends on your particular usage case and requirements. There is no simple, always-true response.

asimpletune 9y ago
What are some examples of each?

whalesalad 9y ago

I cannot think of a single reason to choose Mesos over Kubernetes unless you are literally Twitter.

vicaya 9y ago

FTFA: "We’d previously been using Chronos (with Mesos) as a cron job scheduling system, but it was no longer meeting our reliability requirements and it’s mostly unmaintained (1 commit in the last 9 months, and the last time a pull request was merged was March 2016) Because Chronos is unmaintained, we decided it wasn’t worth continuing to invest in improving our existing cluster." Though Chronos has a release recently with a bunch of fixes, Mesos is inevitably fading as a legacy platform.

asimpletune 9y ago
> Mesos is inevitably fading as a legacy platform. Because of Chronos? This is a bizarre thing to say. Mesos actually works extremely well. Whenever I ask the why kube over Mesos question, I never get a good answer. I think because people just don’t know Mesos. Also it wasn’t made by google.
- vicaya 9y ago
  Chronos is just an example. There're many bugs in Mesos that don't get fixed for months/years. Mesos core is legacy (pre 11) C++ code nobody wants to maintain.
  - pm90 9y ago
    > Mesos core is legacy (pre 11) C++ code nobody wants to maintain. This is actually very very VERY important. Go is a lot more concise (IMO) that C++, generally when I'm curious about how something works in a project written in Go, its much easier to follow the logic.
    - asimpletune 9y ago
      Go is nice. I like it a lot. It's very readable, it reduces the number of good ways you can do something to usually just one, it's fast, fat binaries are awesome, great concurrency primitives, etc...
    - benjamin_mahler 9y ago
      There's something to be said about how the code is written. I've seen easy to read C++ and hard to read go (I found go's built in http server source code to be a tough read) and vice versa. In Mesos we strive to write very readable code and so I would hope that despite being modern C++, it is approachable for an uninitiated reader.
  - asimpletune 9y ago
    This whole thread reads like it's from n-gate.
  - hatred 9y ago
    Please don’t spread FUD when you have no clue what you are talking about. Mesos core is certainly not legacy and has been on C++11 for a long time/is very well maintained and has a large active development community. In case a bug has fell through the cracks; kindly reach out on the user mailing list and I am reasonably confident you would get a response. Disclaimer: Apache Mesos committer/PMC
benjamin_mahler 9y ago
Take a look at the Mesos releases, a lot of progress is being made and and the project is well maintained. Where are you getting this misinformation?