Presentation: Mesos: A State-Of-The-Art Container Orchestrator


11:50am - 12:40pm



Key Takeaways

  • Hear lessons learned building and deploying container technology from a Mesos engineer.
  • Gain better knowledge about different container technologies that are available, such as Docker, Mesos, and Rocket.
  • Learn what’s gone into the Mesos container story as it’s evolved to 1.0.


Mesos, as one of the most powerful container orchestrators, greatly simplifies the deploy, provision and execution of containerized workloads. It automates the distribution of preprovisioned container images, injection of configuration, scheduling onto machines, life-cycle-management, and monitoring of applications, microservices, and jobs in the cloud.

In this talk, Jie Yu will first give you an overview about Mesos and its powerful API which allows users to easily deploy their stateless and stateful services. Then, Jie will talk about how containers are managed in Mesos. In particular, Jie will provide a deep dive into the unified containerizer which is first introduced in Mesos 1.0.

Jie will show some of the new container networking and storage features that are built recently, and how they benefit from the pluggable and extensible architecture of the unified containerizer. Finally, Jie will discuss the future of container support in Mesos.


QCon: What is your role today?

Jie: I currently work at Mesosphere, and my current role is tech lead at the container team. Basically, I work on everything related to containerization, and I lead the projects under that team. 

QCon: Is there anything cool that you're working on and can share with us?

Jie: Mesos has its own containerization engine (it came before Docker). I previously worked at Twitter who's been using Mesos for quite a while. It’s pretty reliable. The thing I’ve been working on is trying to improve the container engine, so it can launch Docker containers or maybe OCI containers (in the future). We are not trying to touch the tools you can use for development from Docker, but, after you push to the registry, we trying to make it where Mesos can take care of everything. So you don’t have to rely on the Docker Daemon. All this has been releasing with Mesos 1.0 and the main thing I’ve been working on.

QCon: How is Mesos actually different than a Docker Daemon?

Jie: Mesos agent is what’s deployed to every host, but it’s not really a Daemon. If you can kill a Daemon, every task goes away.  Mesos can kill the agent at any time, and it will recover everything correctly.  If you want to store some data, we always checkpoint to the disk (so it can recover). Our whole architecture is designed in such a way that it can survive crash elegantly.

I think that’s the main difference.  I think when Docker designed Docker Daemon they didn’t design it in such a way that the assumed Daemon can crash at any time. 

QCon: What do you want people who come to your talk to walk away with?

Jie: I think they will have a better idea about different kinds of container technology (like Docker, Mesos, or Rocket), and have a clearer idea of what the pros and the cons of each of those technologies are. Hopefully, they will want to choose Mesos, and will understand the advantage of  the Mesos container runtime.

QCon: What’s the main focus of your talk?

Jie: I’m going to cover the container side of the story for Mesos 1.0. He did a bunch of work to the containers runtime in 1.0. There are things in there like container network and container storage. The whole thing about the mesos containerization runtime is it’s so pluggable you can do anything you want.

QCon: What does it mean that Mesos is now 1.0?

Jie: I think 1.0 is mainly about the API. Mesos has been in production for several years. People know that it's running in Twitter in production. They know it can handle 30,000 machines in a single cluster. So it’s pretty stable. We could have called it 1.0 a long time ago, but we decided not to because we didn’t have a coherent story for api. Now we do.  So I think 1.0 is mainly about API for the framework providers.

Speaker: Jie Yu

Apache Mesos PMC member, Committer, & SE @Mesosphere

Jie Yu is a Software Engineer at Mesosphere, leading the containerization development in Mesos. Jie is a PMC member of the Apache Mesos project, and one of the top committers. Before joining Mesosphere, Jie was a Software Engineer at Twitter. Jie obtained his PhD in Computer Science and Engineering from the University of Michigan where he conducted research for concurrent and event-driven systems.

Find Jie Yu at

Similar Talks

Developer @ThoughtWorks Inc
Senior Solution Architect @JFrog
Tech Lead of Manhattan Team @Twitter
Staff Engineer, JVM Team @Twitter
Technical Manager Aurora / Mesos Team @Twitter
Provisioning Engineering SE @Twitter
Senior Software Engineer, Playback Features @Netflix



Monday Nov 7

Tuesday Nov 8

Wednesday Nov 9

Conference for Professional Software Developers