StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Product

  • Stacks
  • Tools
  • Companies
  • Feed

Company

  • About
  • Blog
  • Contact

Legal

  • Privacy Policy
  • Terms of Service

© 2025 StackShare. All rights reserved.

API StatusChangelog
Nomad
ByHashiCorpHashiCorp

Nomad

#51in Infrastructure as a Service
Discussions1
Followers344
OverviewDiscussions1

What is Nomad?

Nomad is a cluster manager, designed for both long lived services and short lived batch processing workloads. Developers use a declarative job specification to submit work, and Nomad ensures constraints are satisfied and resource utilization is optimized by efficient task packing. Nomad supports all major operating systems and virtualized, containerized, or standalone applications.

Nomad is a tool in the Infrastructure as a Service category of a tech stack.

Key Features

Handles the scheduling and upgrading of the applications over timeWith built-in dry-run execution, Nomad shows what scheduling decisions it will take before it takes them. Operators can approve or deny these changes to create a safe and reproducible workflowNomad runs applications and ensures they keep running in failure scenarios. In addition to long-running services, Nomad can schedule batch jobs, distributed cron jobs, and parameterized jobsStream logs, send signals, and interact with the file system of scheduled applications. These operator-friendly commands bring the familiar debugging tools to a scheduled world

Nomad Pros & Cons

Pros of Nomad

  • ✓Built in Consul integration
  • ✓Easy setup
  • ✓Bult-in Vault integration
  • ✓Built-in federation support
  • ✓Autoscaling support
  • ✓Self-healing
  • ✓Bult-in Vault inegration
  • ✓Flexible
  • ✓Managable by terraform
  • ✓Multiple workload support

Cons of Nomad

  • ✗Easy to start with
  • ✗HCL language for configuration, an unpopular DSL
  • ✗Small comunity

Nomad Alternatives & Comparisons

What are some alternatives to Nomad?

Apache Mesos

Apache Mesos

Apache Mesos is a cluster manager that simplifies the complexity of running applications on a shared pool of servers.

YARN Hadoop

YARN Hadoop

Its fundamental idea is to split up the functionalities of resource management and job scheduling/monitoring into separate daemons. The idea is to have a global ResourceManager (RM) and per-application ApplicationMaster (AM).

DC/OS

DC/OS

Unlike traditional operating systems, DC/OS spans multiple machines within a network, aggregating their resources to maximize utilization by distributed applications.

kops

kops

It helps you create, destroy, upgrade and maintain production-grade, highly available, Kubernetes clusters from the command line. AWS (Amazon Web Services) is currently officially supported, with GCE in beta support , and VMware vSphere in alpha, and other platforms planned.

Mesosphere

Mesosphere

Mesosphere offers a layer of software that organizes your machines, VMs, and cloud instances and lets applications draw from a single pool of intelligently- and dynamically-allocated resources, increasing efficiency and reducing operational complexity.

Apache Aurora

Apache Aurora

Apache Aurora is a service scheduler that runs on top of Mesos, enabling you to run long-running services that take advantage of Mesos' scalability, fault-tolerance, and resource isolation.

Nomad Integrations

Habitat, Portworx, Consul, Docker, Vault and 4 more are some of the popular tools that integrate with Nomad. Here's a list of all 9 tools that integrate with Nomad.

Habitat
Habitat
Portworx
Portworx
Consul
Consul
Docker
Docker
Vault
Vault
Hashicorp Sentinel
Hashicorp Sentinel
HashiCorp Waypoint
HashiCorp Waypoint
Gloo Edge
Gloo Edge
Humio
Humio

Try It

Visit Website

Adoption

On StackShare

Companies
74
CITSSL+68
Developers
196
SJLMHI+190

Nomad Discussions

Discover why developers choose Nomad. Read real-world technical decisions and stack choices from the StackShare community.

Robert Zuber
Robert Zuber

CTO at CircleCI

Jul 24, 2019

Needs adviceonDockerDockerKubernetesKubernetesNomadNomad

Our backend consists of two major pools of machines. One pool hosts the systems that run our site, manage jobs, and send notifications. These services are deployed within Docker containers orchestrated in Kubernetes. Due to Kubernetes’ ecosystem and toolchain, it was an obvious choice for our fairly statically-defined processes: the rate of change of job types or how many we may need in our internal stack is relatively low.

The other pool of machines is for running our users’ jobs. Because we cannot dynamically predict demand, what types of jobs our users need to have run, nor the resources required for each of those jobs, we found that Nomad excelled over Kubernetes in this area.

We’re also using Helm to make it easier to deploy new services into Kubernetes. We create a chart (i.e. package) for each service. This lets us easily roll back new software and gives us an audit trail of what was installed or upgraded.

0 views0
Comments