Win a copy of Pro Spring MVC with WebFlux: Web Development in Spring Framework 5 and Spring Boot 2 this week in the Spring forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Jeanne Boyarsky
  • Liutauras Vilda
  • Rob Spoor
  • Bear Bibeault
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Piet Souris
  • Frits Walraven
  • Himai Minh

Mesos in Action: Mesos vs. Kubernetes

Posts: 93
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Roger,

Hearty congratulations for your book - and the book looks quite interesting.

I have a question regarding Mesos vs. Kubernetes. What are the factors to consider when choosing between Mesos or Kubernetes? Is it possible to use Kubernetes on Mesos?

Thanks and wishing great success for your book

Best regards,
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thank you!

Disclaimer: I work at Mesosphere.

The way I see it, when you're comparing tools for container operations you need to consider a few basic things (among many others!):
  • Resource scheduling
  • Container orchestration
  • Service discovery

  • In the Mesos ecosystem, Mesos acts as the kernel that pools all of the resources of a large number of machines together as if they're one machine. This then allows other projects, such as Marathon or Aurora, to launch workloads on the underlying Mesos cluster. Then when it comes to something like service discovery within the cluster, you can take a look at mesos-dns, Consul-Mesos, etc. All of this follows the Unix philosophy of "a tool should do one thing and do it well", something I'm a huge fan of. It allows you to pick components you feel comfortable with (or write your own!) and assemble the stack that way.

    DC/OS aims to shrink-wrap all of these into one installable package, which you may or may not be a fan of depending on your goals and personal preference.

    Kubernetes, on the other hand, attempts to tackle all three in one project, similar to DC/OS. The thing with Kubernetes though is that I believe the folks at Google have focused first on the developer APIs to make that a great experience, and are now playing catch-up a bit on the enterprise features and scalability of the platform. In the latest release (1.3 as of my post here) they seem to be doing a great job.

    So, in short, it really depends on your organization and level of comfort. I'd recommend trying out each (links below!) and figuring out a) which one you're more comfortable with running in production, and b) what makes the most sense for your team. As for running Kubernetes on Mesos, I honestly don't know how actively that's being developed anymore. You might have a look at and

    If this is too high level, please feel free to post a follow-up here and I can dig in with more specifics.

    Links to try out Mesos, DC/OS, and Kubernetes:
    This one time, at bandcamp, I had relations with a tiny ad.
    Thread Boost feature
      Bookmark Topic Watch Topic
    • New Topic