Docker Container Orchestration: What You Need to Know

Kubernetes. Mesos. Marathon. Centurion. If you’re a newcomer to Docker containers, these names probably sound like terms from a classical history book. But they’re actually container orchestration platforms. And they’re only a few of them. Confused? Here’s what you need to know about container orchestration.

To understand container orchestration, you first need to understand containers, of course. Today, when people talk about containers, they’re referring to virtualized apps that use the LXC layer in the Linux kernel to abstract code from the underlying system.

On their own, containers only let you run individual apps. That doesn’t make them very useful. If you just want to run a few apps you can do it more easily without containers.

But if you have a large number of apps to run — as you likely do if you have migrated to the cloud — containers come in handy. They make it easy to turn apps on and off to meet fluctuating demand. They also let you move apps seamlessly between different servers.

Unless you’re super-human, though, you can’t move container apps around very efficiently on your own. You need a management platform that will automatically spin containers up, suspend them or shut them down when needed — and, ideally, also control how they access resources like the network and data storage.

That’s where orchestration platforms come in. They provide this piece of the container puzzle.

Decisions, Decisions

The container ecosystem is basically open source. Open source programmers like choice. So it’s no surprise that there are now dozens of orchestration platforms that can handle containers.

Discussing all of them here would make for a very long read. So we’ll outline just the top orchestration platforms:

Again, we could go on. But we think these are the essentials. If your favorite container orchestration tool is not listed here, feel free to let us know why you think it should be.