Nomad vs Mirantis Kubernetes Engine (Docker Enterprise)

• Nomad is incredibly simple by nature, following the Linux philosophy of doing one thing great. That one thing for Nomad is job scheduling.
• Nomad is a modern tool, written in Go with a large community and maintained by HashiCorp.
• Implementation of Nomad is very simple since it is a single binary.

Read full review

• Containers - Docker is the go-to when using Containers, which are super useful if you need an environment that works both for Windows and Linux
• Efficiency - Docker is very lightweight and doesn't demand too much from your CPU or server
• CI/CD - Docker is excellent for plumbing into your build pipeline. It integrates nicely, is reliable, and has an easy set up.

Read full review

• Nomad only handles one part of a full platform. Expertise and vision are required in implementing an entire system that is functional enough for an organization to rely on. This includes other tools to handle things like secrets, service discovery, network routing, etc.
• Nomad is delayed in some modern functionality, like features for service-mesh and open tracing. These features are on the tool's roadmap, but there's currently no native support. These paradigms can be established still, but require more expertise outside of Nomad itself.
• Nomad is not the leading tool for this space, and as such risks being left behind by tools with much greater support, such as Kubernetes.

Read full review

• Containers are often opaque - if a container doesn't work out of the box, it's messy to fix.
• Logging is complexified by the multiple containers and logs are often not piped to places you expect them to be.
• Networking is complexified due to internal port mapping between containers, etc.

Read full review

• Nomad has allowed our organization to deploy quicker and more frequently with a lower failure rate.
• Nomad has brought in consistency from an operations perspective.
• Nomad's performance allows us to scale infinitely while providing functionality that reduces mean time to repair (canary deploys, versioning, rollbacks, etc).

Read full review

• Docker has made it possible for us to deploy code faster, increasing the productivity of our development teams.
• Docker has made it possible for us to decentralize our build and release system. This means that teams can deploy on their own schedule and our dev ops team can concentrate on building better tools rather than deploying for the teams
• Docker has allowed us to virtualize our entire development process and made it much simpler to build out new data centers. This, in turn, is significantly increasing our ROI by providing a path forward for internationalization.

Read full review