The importance of scale may be over-rated as current container deployments are still relatively small.
The buzz around Kubernetes is undeniable, with it seeing increased meetup activity and many vendors planning solutions based on it. And Docker’s native Swarmkit continues to be attractive to the large group of people interested in a simple way to start using containers. Among the other container orchestration approaches, the ability to handle scale is the calling card of the combination of Mesos and Marathon.
The creators of Apache Mesos founded Mesosphere and went on to create DC/OS, which since last April has been available in both enterprise and open source versions. DC/OS is being pitched for container management to the Mesos community, which uses it with Big Data frameworks more often than large scale deployments.
We last wrote about these tools’ relative adoption levels in July. In recent days, OpenStack Foundation issued a user survey that indicates that Kubernetes is the leading choice in the community, with many telcos and service providers using it. And last week Mesosphere published a report about another community, about Apache Mesos users.
When looking just at adoption of container management offerings, the study’s bias is undeniable. This report shows that Mesosphere-backed DC/OS is being used or piloted for broader deployment 38 percent of respondents, as opposed to 19 percent for Kubernetes and 15 percent for Docker Swarm. Many respondents are using or considering multiple container orchestration tools simultaneously. The big caveat emptor is that in addition to soliciting Apache Mesos contributors for responses via the Apache’s Mesos’ mailing lists, the survey was also sent to the Mesosphere’s entire client and prospect list.
We believe there are still valuable insights to be found since many of the company’s prospects were identified because they already use Mesos.
In the last two years, Mesos contributors have more than doubled, but it hard to ascertain what has driven that growth. It could be because developers are flocking to its ability to orchestrate containers, or perhaps Big Data developers are the reason. Another hypothesis is that the use of DC/OS itself is driving community involvement. Among the people taking the survey, 63 percent had been using Mesos for less than a year. Among those using it for fewer than six months, 89 percent were introduced to it via DC/OS.
Of the Mesos users surveyed, 62 percent are using containers in production. We do not know how many of these were using containers and then decided to use DC/OS. However, we do know that the level of container usage is much higher than seen among the broader IT population. Including those that do not have production use, 85 percent are running “containers — microservices architecture” workloads on Mesos.
The average respondent is running three or more frameworks on Mesos. The most common is Marathon, deployed by 83 percent. No wonder DC/OS now includes that scheduling functionality baked in. Frameworks for deploying data services are being deployed on top of Mesos by 68 percent of respondents. Among those big data frameworks, Spark is the most often deployed, followed by Kafka, Elasticsearch and Cassandra.
Many are using multiple data frameworks together, which supports the hypothesis that a new SMACK stack is gaining popularity. Mesos’ ability to work with multiple frameworks, including Kubernetes, provides flexibility in terms of choosing a container management platform. Of course, when deployed using DC/OS, there may be more “opinions” introduced. When just looking at container orchestration engines, a recent Rancher blog post, claims it is easier to deploy non-containerized applications with Mesos as compared to Kubernetes.
The biggest selling point for Mesos is that it has been tested at scale. In fact, at 56 percent, scale was the top reason respondents chose Mesos. However, it is important to realize that many users don’t actually need that scale. In fact, among respondents using Mesos for more than six months, only a quarter have more than 100 machines running in a cluster, with only 4 percent running more than 1,000. While cluster sizes are larger among bigger companies and those that have been using Mesos longer, this stat is cause for concern. Some Kubernetes advocates say that most companies don’t need Twitter-sized scale. If they are right, then DC/OS loses one of its advantages.
Questions for Future Research
- Do people want to use multiple container orchestration systems? Will they use Mesos and Kubernetes concurrently?
- Will Mesosphere be able to convert Mesos users into DC/OS customers?
- Does strong exposure to Big Data use cases offer Mesos, and consequently Mesosphere, an advantage?
Feature image: The Apache Software Foundation