Azure Batch
Azure Batch is a cloud service which enables running large-scale applications parallel and high-performance computing (HPC) batch jobs efficiently in the cloud, schedule compute-intensive tasks, and dynamically adjust resources for your solution without managing infrastructure. Here is the official document [here], as a short version of my understanding, it is a way to run batch jobs on Cloud with (almost) no effort on orchestration, no cluster, or job scheduler software to install, manage, or scale. And the charge for Azure Batch is lower, you only pay for the underlying resources consumed, such as the virtual machines, storage, and networking.
According to Microsoft's document, Azure Batch Service might is the best option to run a big computing job while it does not require low latency.
The following table is from [here] which is a breakdown of different kinds of apps and their possible/recommended Azure hosting scenarios.
Application Architecture
VMs - Azure Virtual Machines
ACI - Azure Container Instances
Azure App Service (w-w/o containers)
AKS - Azure Kubernetes Services
Azure Functions
Azure Batch
Web apps (Monolithic)
![]()
![]()
![]()
![]()
N-Tier apps (Services)
![]()
![]()
![]()
![]()
![]()
Cloud-Native (Microservices)
![]()
(Linux containers)
(Event‑driven)
Batch/Jobs (Background tasks)
![]()
![]()
![]()
![]()
(Background tasks)
(Large‑scale)
Legend
Recommended
Possible
Last updated
Was this helpful?