Visit us on Discord or Discourse to give us some feedback or chat.
| 3 Recommended Products | Recommendations | Price | Last Updated |
|---|---|---|---|
| #1 Docker Swarm· · · | 4 | 1 | – | Jun 13, 2017 |
| #2 Kubernetes· · · | 4 | 0 | – | Jul 28, 2016 |
| #3 Nomad· · · | 1 | 0 | – | Apr 4, 2016 |
Pro Communicates with other Docker tools easily
Since Docker Swarm is a native Docker tool, it exposes the Docker API, making it possible to integrate it and communicate with other Docker tools (CLI, Compose, Krane, etc.).
Pro Easy setup
This also means that containers can be launched with a simple docker run command and Swarm will take care of the rest, such as selecting the appropriate host on which to run the container.
Con Bounded by the limitations of the Docker API
If the Docker API doesn't support something, then you are pretty much out of luck when it comes to Docker Swarm, because it won't be supported by Swarm either.
Pro Built on several years of experience with Docker containers
Kubernetes was built on top of several years of experience from Google working on containers in production. It's a little opinionated on how containers should work and behave, but if used correctly it can help you achieve fault-tolerant systems.
Pro Supported on several PaaS
Kubernetes is currently supported by Google Compute Engine, Rackspace, Microsoft Azure, and vSphere. Work is being done to support Kubernetes on OpenShift and CloudFoundry.
Con If used on an existing system, some re-organizing may be needed
Because of how opinionated Kubernetes is, it may be necessary to change some things if you decide to use Kubernetes as an orchestration tool in an existing application.
Con Cannot define containers through the Docker CLI
Kubernetes was not written for docker clustering alone. It uses a different API, configuration and different YAML definitions. So you can't use the Docker CLI or Docker Compose to define your containers. Everything has to be done from scratch.
Pro JSON based HTTP API
You can control and monitor jobs via a JSON based HTTP API. There is even the concept of a blocking query whereby you can use long pulling to wait for status updates about running jobs.
Pro Not just Docker
Nomad schedules many different types of tasks via Drivers, including: docker containers, forking processes, running jar files, rkt and VMs via QEMU. See more here https://www.nomadproject.io/docs/drivers/index.html
Con Not a complete tool
While other orchestration tools provide much more than just cluster management and scheduling (they also provide things like secrets management, discovery, monitoring, etc.), Nomad follows the Unix philosophy of doing only one thing and doing it well, providing only cluster management and scheduli...
Comments
Welcome to the Slant Community
Stop spending hours researching
Slant is written by a community helping you be informed. Let us know what you’re passionate about to get an awesome personalized feed.