Answers: <p>Your impression is false, linux containers (LXC) exists since 2008, mesos and docker have started later. All three makes use of cgroups available since kernel 2.6.28. </p>
  
  <p>For your overall question, mesosphere have a <a href="https://mesosphere.com/blog/docker-vs-kubernetes-vs-apache-mesos/" rel="nofollow noreferrer">blog post</a> about it. </p>
  
  <p>But mainly you're looking at it from the wrong point of view, choosing the underlying orchestration system should not be done from 'how to deploy this application?' point of view, but more on 'What would be the best orchestration for what I have to deploy as a whole ?'. Making the choice between swarm/kubernetes/mesos/k8s on mesos/swarm on mesos/whatever is very dependent on your environment, your existing knowledge, your team skills etc. and we can"'t really help you choose without an extended description on what you're willing to manage.</p>
  
Answers: CC BY-SA 3.0
Answers: 2018-04-10T08:20:20.140Z
Answers: "linux containers (LXC) exists since 2008" I've added "easily avalable"
Answers: Ta Mu
Answers: CC BY-SA 3.0
Answers: 2018-04-10T12:06:32.387Z
Answers: @PeterMuryshkin easily is very personal, I did found legacy lxc easier to work with than docker for a bunch of cases, either you're asking about docker (and in this case yes, mesos was a little earlier than docker, 2k11 vs 2k13) ,marathon was in 2k14 but would more compare to swarm). All in all, the blog post I linked gives the general difference nowadays and the uses cases, the answer stands after the edit as it is still the same, choosing the underlying orchestration should not be taken from a single application point of view but from a global architecture point of view.
Answers: Tensibai
Answers: CC BY-SA 3.0
Answers: 2018-04-10T07:41:04.843Z
Answers: 2018-04-10T07:41:04.843Z
Answers: Tensibai
Body: <p>My current impression is, Apache Mesos was introduced before the LXC container technology became <em>easily</em> available (via Docker).</p>
  
  <p>So you could implement "your own Apache Mesos Java framework" for example, or use Marathon to do that.</p>
  
  <p>Now, Marathon seems to support containers as well.</p>
  
  <p>Question - when would you deploy Java nowadays on/with Mesos/Marathon without contauners? And if you use containers, why should you opt for Mesos instead of for example Kubernetes?</p>
  
  <p>For example, <a href="https://logz.io/blog/kubernetes-vs-mesos/" rel="nofollow noreferrer">here</a> they say in my understanding, k8s ecosystem deployment is easier while with Mesos you would have to opt for the enterprise version of DC/OS. </p>
  
Tags: <containers><orchestration>
Title: Apache Mesos - cases pro and contra containers?
UserDisplayName: Ta Mu
ThreadText: # Apache Mesos - cases pro and contra containers?
  
  (Asked by: username_0 on 2018-04-10)
  
  My current impression is, Apache Mesos was introduced before the LXC container technology became *easily* available (via Docker).
  
  So you could implement "your own Apache Mesos Java framework" for example, or use Marathon to do that.
  
  Now, Marathon seems to support containers as well.
  
  Question - when would you deploy Java nowadays on/with Mesos/Marathon without contauners? And if you use containers, why should you opt for Mesos instead of for example Kubernetes?
  
  For example, [here](https://logz.io/blog/kubernetes-vs-mesos/) they say in my understanding, k8s ecosystem deployment is easier while with Mesos you would have to opt for the enterprise version of DC/OS.
  
  **Tags:** containers, orchestration
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-04-10. Score: 1 | Accepted answer
  
  Your impression is false, linux containers (LXC) exists since 2008, mesos and docker have started later. All three makes use of cgroups available since kernel 2.6.28.
  
  For your overall question, mesosphere have a [blog post](https://mesosphere.com/blog/docker-vs-kubernetes-vs-apache-mesos/) about it.
  
  But mainly you're looking at it from the wrong point of view, choosing the underlying orchestration system should not be done from 'how to deploy this application?' point of view, but more on 'What would be the best orchestration for what I have to deploy as a whole ?'. Making the choice between swarm/kubernetes/mesos/k8s on mesos/swarm on mesos/whatever is very dependent on your environment, your existing knowledge, your team skills etc. and we can"'t really help you choose without an extended description on what you're willing to manage.
  
  > **Comments:**
  > **username_0**: "linux containers (LXC) exists since 2008" I've added "easily avalable"  
  > **username_1**: @PeterMuryshkin easily is very personal, I did found legacy lxc easier to work with than docker for a bunch of cases, either you're asking about docker (and in this case yes, mesos was a little earlier than docker, 2k11 vs 2k13) ,marathon was in 2k14 but would more compare to swarm). All in all, the blog post I linked gives the general difference nowadays and the uses cases, the answer stands after the edit as it is still the same, choosing the underlying orchestration should not be taken from a single application point of view but from a global architecture point of view.  
  
  ---
  
  