github.com/anth0d/nomad@v0.0.0-20221214183521-ae3a0a2cad06/website/content/intro/use-cases.mdx (about) 1 --- 2 layout: intro 3 page_title: Use Cases 4 description: |- 5 This page lists some concrete use cases for Nomad, but the possible use cases 6 are much broader than what we cover. 7 --- 8 9 # Use Cases 10 11 This page features Nomad's core use cases. 12 13 Note that the full range of potential use cases is broader than what is covered here. 14 15 ## Docker Container Orchestration 16 17 Organizations are increasingly moving towards a Docker centric workflow for 18 application deployment and management. This transition requires new tooling 19 to automate placement, perform job updates, enable self-service for developers, 20 and to handle failures automatically. Nomad supports a [first-class Docker workflow](/docs/drivers/docker) 21 and integrates seamlessly with [Consul](/docs/integrations/consul-integration) 22 and [Vault](/docs/integrations/vault-integration) to enable a complete solution 23 while maximizing operational flexibility. Nomad is easy to use, can scale to 24 thousands of nodes in a single cluster, and can easily deploy across private data 25 centers and multiple clouds. 26 27 ## Legacy Application Deployment 28 29 A virtual machine based application deployment strategy can lead to low hardware 30 utilization rates and high infrastructure costs. While a Docker-based deployment 31 strategy can be impractical for some organizations or use cases, the potential for 32 greater automation, increased resilience, and reduced cost is very attractive. 33 Nomad natively supports running legacy applications, static binaries, JARs, and 34 simple OS commands directly. Workloads are natively isolated at runtime and bin 35 packed to maximize efficiency and utilization (reducing cost). Developers and 36 operators benefit from API-driven automation and enhanced reliability for 37 applications through automatic failure handling. 38 39 ## Microservices 40 41 Microservices and Service Oriented Architectures (SOA) are a design paradigm in 42 which many services with narrow scope, tight state encapsulation, and API driven 43 communication interact together to form a larger solution. However, managing hundreds 44 or thousands of services instead of a few large applications creates an operational 45 challenge. Nomad elegantly integrates with [Consul](/docs/integrations/consul-integration) 46 for automatic service registration and dynamic rendering of configuration files. Nomad 47 and Consul together provide an ideal solution for managing microservices, making it 48 easier to adopt the paradigm. 49 50 ## Batch Processing Workloads 51 52 As data science and analytics teams grow in size and complexity, they increasingly 53 benefit from highly performant and scalable tools that can run batch workloads with 54 minimal operational overhead. Nomad can natively run batch jobs and [parameterized](https://www.hashicorp.com/blog/replacing-queues-with-nomad-dispatch) jobs. 55 Nomad's architecture enables easy scalability and an optimistically 56 concurrent scheduling strategy that can yield [thousands of container deployments per 57 second](https://www.hashicorp.com/c1m). Alternatives are overly complex and limited 58 in terms of their scheduling throughput, scalability, and multi-cloud capabilities. 59 60 ## Multi-Region and Multi-Cloud Federated Deployments 61 62 Nomad is designed to natively handle multi-datacenter and multi-region deployments 63 and is cloud agnostic. This allows Nomad to schedule in private datacenters running 64 bare metal, OpenStack, or VMware alongside an AWS, Azure, or GCE cloud deployment. 65 This makes it easier to migrate workloads incrementally and to utilize the cloud 66 for bursting.