HashiCorp Nomad vs Kubernetes - Comparing Complexity
Learn about HashiCorp Nomad: Why it's simpler than Kubernetes, how to set up a cluster, and how to integrate it with most of your existing legacy services and infrastructure.
Andy Davies is a software developer at Reaktor, a software consultancy. In his recent talk at Codemotion Rom 2019, he tried to temper some of the hype around Kubernetes, specifically arguing that it wasn't the best fit for every orchestration problem and that it adds a lot of operational complexity to an organization.
In fact, Davies suggests that you should almost never try to deploy Kubernetes yourself—get a cloud provider to do it for you. "You're reselling Kubernetes as a service" if you try to roll your own setup, he says. "It's a waste of your company's money."
His talk, titled "Nomad: Kubernetes without the Complexity" dives into several demos of an alternative cluster scheduling solution called HashiCorp Nomad. Instead of trying to solve all of the things that Kubernetes tries to solve:
- Service discovery
- Load balancing
- Configuration management
- Secret storage
- Feature gates
- Storage orchestration
- Container management
- Rollouts & rollbacks
Nomad just focuses on scheduling. It does have some storage orchestration capabilities but mainly it is built to be a bridge between orchestrating newer container-based infrastructures and older VM, binary, or other workload-based infrastructures. In one Nomad cluster, you can run Docker containers, VMs, and Java JARs—as an example. Kubernetes, on the other hand, is mostly built for containers only.
In this talk, Davies will demo several features of Nomad to showcase its capabilities. He'll demonstrate how to set up Nomad a cluster, deploy containers and applications to it, and then integrate it with existing services and infrastructure.