Container Instances

Azure Container Instances (ACI) can be used for running application workloads, allows business to focus on designing and building applications instead of managing the infrastructure that runs.

Containers are becoming the preferred way to package, deploy, and manage cloud applications. Azure Container Instances offers the fastest and simplest way to run a container in Azure, without having to manage any virtual machines and without having to adopt a higher-level service.

Azure Container Instances is a great solution for any scenario that can operate in isolated containers, including simple applications, task automation, and build jobs. For scenarios where you need full container orchestration, including service discovery across multiple containers, automatic scaling, and coordinated application upgrades, itreen recommend Azure Kubernetes Service (AKS).

Elastic bursting with AKS

ACI provides fast, isolated compute to meet traffic which comes in spikes, without the need to manage servers. For example, Azure Kubernetes Service (AKS) can use the Virtual Kubelet to provision pods inside ACI that start in seconds. This enables AKS to run with just enough capacity for your average workload. As you run out of capacity in your AKS cluster, scale out additional pods in ACI without any additional servers to manage.

Event-driven applications with Azure Logic Apps

Combine ACI with the ACI Logic Apps connector, Azure queues and Azure Functions to build robust infrastructure which can elastically scale out containers on demand. With Azure Container Instances, you can run complex tasks which are capable of responding to events.

Data processing jobs

Use Azure Container Instances for data processing where source data is ingested, processed and placed in a durable store such as Azure Blob storage. By processing the data with ACI rather than statically-provisioned virtual machines, you can achieve significant cost savings through per-second billing.