When choosing an orchestrator / scheduler, there are several solutions to compare.
When choosing an orchestrator / scheduler, there are several solutions to compare.
The most popular examples include: - Kubernetes - Mesos with Marathon - Amazon ECS - Docker Swarm - HashiCorp Nomad
The first area of comparison is what kind of jobs each orchestrator can handle.
Many of the orchestrators assume that organizations will rebuild services to use only containerized Docker workloads, so there isn't as strong of an integration workflow for any heterogeneous or hybrid strategy that involves a bi-modal IT migration strategy.
Nomad integrates with hybrid infrastructures - Can Bin-pack more than just containers - Support for Raw & Isolated Executables, Java .jar files, and more - Open source task driver for custom workload support
Ease of Use - Nomad allows you to use a single Job file across hybrid infrastructures - Job files are written in HCL, not YAML
Istio service mesh (service mesh helps provide zero trust networking doesn't work as easily outside Kubernetes clusters. This can make service mesh and integration between Kubernetes and non-Kubernetes systems difficult.)
Nomad works out-of-box with the more heterogeneous-friendly Consul HashiCorp Consul (and it's service mesh Connect feature)is built right into Nomad. So integration between Nomad and non-Nomad technologies is easy.
Nomad works out-of-box with HashiCorp Vault, one of the most trusted secrets management tools Vault is also built right into Nomad, meaning getting encrypted secrets into applications
To learn how to use Nomad, visit the Nomad Track on HashiCorp Learn. For enterprise use cases, visit the Nomad product page and please get in touch.