Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Docker vs. Kubernetes vs. Mesos

mesosphere.com

Post reply on HN
Print view View original

21–30 of 79 posts

Re: Docker vs. Kubernetes vs. Mesos

#21

Post by majewsky »

manojlds wrote: post #13
pebers wrote: post #11

I guess I should expect some bias given the publisher, but despite a good technical write-up of the difference, their conclusions aren't really backed up by the rest of the article and the wording is obviously slanted towards their own product. > While there are multiple initiatives to expand the scope of the project to more workloads (like analytics and stateful data services), these initiatives are still in very ea…

They said legacy applications. You can run a command or script or binary in Mesos / marathon. In Kubernetes, you can run only containers. So at the minimal, your legacy app has to be containerized / dockerized.

> You can run a command or script or binary in Mesos / marathon.

Where does the binary come from, if not from a container?

Re: Docker vs. Kubernetes vs. Mesos

#22

Post by caspereeko »

I would like to share my personal experience running Meoss.

I have been using Pure Mesos setup, without DC/OS for 2.5 years.

We have the following infra features.:

- 120 micro-services running using marathon.

- 10 batch jobs running using Chronos.

- So far, everything is reliable and no downtime.

- We have Ip-Per-Task enabled with Project Calico.

- We have Public, Private, and IP Access-list enabled per container using Nginx and ELBs.

- The max number of containers we ran on the cluster so far is 3620 containers.

- We have detailed graphs monitoring per-container generated automatically.

- We have (slack #alerts) alerting enabled.

- We have secrets store using vault.

In the end we had to use (Mesos, Marathon, Chronos, Vault, Consul, Nginx, Calico, ELK, TICK.) on AWS.

The thing is, We had to configure these things to work together nicely so it is not out-of-the-box solution. Even though we haven't used Kubernetes yet, we are not religious to Mesos.

But at the moment, it seems we have everything we need and the team is happy with the current setup.

Re: Docker vs. Kubernetes vs. Mesos

#23

Post by x0rg »

Izmaki wrote: post #6
x0rg wrote: post #5

Those kind of articles are not so useful, Mesosphere is the company behind DC/OS and Mesos and they have all the interest in the world to say that Mesos is the best. Things like "... are willing to get your hands dirty integrating your solution with the underlying infrastructure" when talking about Kubernetes is unfair, especially if you compare Kubernetes to Mesos and not to Mesosphere DC/OS for which they provide p…

Some of us love getting our hands dirty. In my honest opinion this whole article seemed very neutral in phrasing. It wasn't until I decided to check the source after having read and enjoyed the entire article, that I discovered that it was written in a Mesos domain. And even then I applaud that they were humble enough to save their own product until the end and didn't seem to exaggerate their sales pitch.

True, it is not too much of a sales pitch, but still something that really can't be seen as impartial, for natural reasons (it comes from the company behind Mesos) and it looses a bit of clarity (Java doesn't equal legacy, you can run Stateful workloads on Kubernetes) towards the end.

From my point of view, the benefits of the two level scheduling are actually quite limited with respect to how the whole story is usually told. Some Mesos framework always use all the resources from the clusters and it might get tricky to really have multiple frameworks to run at the same time on Mesos. Also, sometimes those frameworks don't really offer so many additional features to justify changing the way you are already using Spark, Cassandra and so on.

Re: Docker vs. Kubernetes vs. Mesos

#24

Post by LoSboccacc »

weird they say Kubernets are more comparable to Docker in Swarm Mode than Docker standalone, but then list the features of Docker standalone

not that I'd endorse swarm mode eh, it's very very early stages and lacks a truckload of features before it could be used in anything but the simplest node replication scenarios.

Re: Docker vs. Kubernetes vs. Mesos

#25

Post by Illniyar »

ec109685 wrote: post #19
x0rg wrote: post #5

Those kind of articles are not so useful, Mesosphere is the company behind DC/OS and Mesos and they have all the interest in the world to say that Mesos is the best. Things like "... are willing to get your hands dirty integrating your solution with the underlying infrastructure" when talking about Kubernetes is unfair, especially if you compare Kubernetes to Mesos and not to Mesosphere DC/OS for which they provide p…

One more difference is Mesos is written in C++, while Kubernetes is written in Go.

Is that relevant?

Re: Docker vs. Kubernetes vs. Mesos

#27

Post by davidopp_ »

ej_campbell wrote: post #16
x0rg wrote: post #5

Those kind of articles are not so useful, Mesosphere is the company behind DC/OS and Mesos and they have all the interest in the world to say that Mesos is the best. Things like "... are willing to get your hands dirty integrating your solution with the underlying infrastructure" when talking about Kubernetes is unfair, especially if you compare Kubernetes to Mesos and not to Mesosphere DC/OS for which they provide p…

The Kubernetes folks talk about the differences here and how you could build Mesos apps in K8s: https://github.com/davidopp/kubernetes/blob/87f2590f373306ea... The limitation of only being able to run Containers I think will be fleeting — as docker and alternatives mature, it really won't make sense to ever use anything else when trying to get the scale that Kubernetes and Mesos is going for by abstracting out the un…

What's described in that doc is even easier today thanks to Operators (https://coreos.com/operators), which, to quote the description page, are "application-specific controller[s] that extend[s] the Kubernetes API to create, configure and manage instances of complex stateful applications on behalf of a Kubernetes user."

Disclosure: I work on Kubernetes at Google (and wrote the doc you linked to).

Re: Docker vs. Kubernetes vs. Mesos

#28

Post by davidopp_ »

conradk wrote: post #15

I recently evaluated all 3 solutions. Here is how I see it after testing the waters: - want something simple that works today? Docker Swarm - want something amazingly flexible? Kubernetes - already use Mesos or DC/OS? Marathon/Mesos This article from Mesosphere is interesting and gives a good overview, but it downplays advantages of Swarm and Kubernetes and clearly highlights Mesos: Docker has 4 bullet points, Kubern…

Kubernetes runs on GCP, AWS, and Azure, and in various on-prem configurations (including on OpenStack).

Disclosure: I work on Kubernetes at Google.

Re: Docker vs. Kubernetes vs. Mesos

#29

Post by gotbeans »

Illniyar wrote: post #25
ec109685 wrote: post #19

Earlier quoted context omitted.

One more difference is Mesos is written in C++, while Kubernetes is written in Go.

Is that relevant?

He at least did give information about the topic at hand

Edit: I apologize to the readers, this is not the right place for this kind of talk

Post reply on HN