Azure Container Instances vs App Service

Microsoft Azure platform offers a wide range of services ready to use during creation and deployment processes of our containerized applications happening in the cloud.

Considering the multiplicity of available solutions – it is worth being aware of different hosting services (so-called Azure Compute Services, Hosting Services) details. This knowledge will greatly improve our ability to make a choice that matches our needs in terms of architectural decisions.

Hosting services are categorized into groups because of different hosting models.

We can indicate following models:

  • IaaS (Infrastructure as a service)
  • PaaS (Platform as a Service)
  • SaaS (Software as a service)

which determine the way of how the resources are being used in the cloud and what their usage scope is.

There are plenty of factors that can (and potentially should) affect our decisions, but during the early phase of research it can be crucial to answer questions such as:

  • How much control do we need?
  • Where do we want to use our application? (on-premise, hybrid cloud, public cloud)
  • What will be the main way of usage? (continuous or on-demand usage)

Solutions from the IaaS group usually provide more control with simultaneous increased responsibility for created resources. On the other hand – SaaS solutions gives less control while freeing us from most resource-management related tasks.

The final choice targeting production should be always preceded by an analysis of different Azure services capabilities versus main goal and scope of designed software.

In this article I would like to discuss features, pros, cons, as well as differences between two Azure Hosting PaaS services used during development and deployment processes of containerized applications:

  • Azure Container Instances (ACI)
  • Azure App Service

This service was created primarily with ease of use in mind. It supports both Windows and Linux containers. ACI provides very basic functionalities for creating and managing a group of containers. If our main target is to quickly start a new container with our application without going too deep into details related to configuration and orchestration – this will be the most common choice.

In most cases, using Azure Container Instances requires only:

  • Providing a docker container image,
  • Specifying base configuration (number of required CPU cores or memory size)

Among key advantages of this service we can indicate:

  • Fast startup time (usually couple seconds),
  • Billing only for real usage (payment per second of service activeness) without any initial costs,
  • No need for complex orchestration implementation,
  • Providing container isolation level similar to security level provided by running applications on different virtual machines,
  • Availability of public IP addresses for containers which can be accessible from Internet using FQDN (Fully Qualified Domain Name),
  • Option to integrate with Azure Kubernetes Service,
  • Option to deploy a group of containers (ACI Container Groups) on one host machine using shared storage space, shared network and other resources between containers working together towards one goal

Some of ACI disadvantages are:

  • Limited scalability – in terms of scaling up – ACI provides options to define resources allocated for a container. However, scaling out requires manual creation and management of ACI instances. It also does not provide auto-scaling.
  • Basic configuration – in certain scenarios it becomes a drawback (i.e. lack of port mapping functionality can force us to modify the code of the container to make it play well with ACI).

Below you can see a simplified diagram presenting a deployment process of application using Azure Container Instances:

It is a service often called a „fully-featured” offering for hosting applications. 

Azure App Service provides access to every tool needed during development and deployment processes of web applications that are growing, and which business scope is constantly changing over time.

It offers a lot of integration capabilities in terms of other Azure services. Running containers with applications is only a small subset of overall App Services functionalities.

We can think of this service as a framework providing us with necessary tooling for the whole software development cycle.

Azure App Service advantages worth mentioning are:

  • High availability (guaranteed 99.5% availability basing on SLA contracts),
  • Automatic or manual scaling in and out with option to specify the scaling rules,
  • Load-balancing
  • Built-in security mechanisms related to authentication and authorization processes (i.e. two-factor authentication)
  • Support for many programming languages,
  • Built-in SSL certificates management
  • Great integration with IDE tools for deploying apps,
  • Deployment Slots functionality which is free, and allows environment duplication – commonly used for testing application before going live,
  • Support for code, container or even binaries based deployments

Some of this service disadvantages are:

  • Complexity – forcing to learn about many details related with service operation,
  • Dedicated mostly for web applications, other types of apps support is limited,
  • Usage of services delivered by one cloud provider (in this case Azure) not always translates into universal skills

Below you can see a simplified diagram presenting deployment process of application using Azure App Service:

After analyzing the key features of both presented services, one can get an impression that they have some common parts. However, they were built for other purposes.

Azure Container Instances is a lightweight hosting service allowing us to quickly spin up a new container with our application. Its scope is usually well-known, and functionalities are rather basic. ACI might be a good choice if plans on expanding and scaling the application do not play a huge role, due to its predictable use.

For comparison – Azure App Service is some kind of an ecosystem providing suitable tools and elasticity. Similarly to ACI, it uses containerization for running applications but in addition focuses on the whole software development process, and will work perfectly for complex web applications that are growing constantly. Factors such as high availability, scalability or plenty of possible out of the box integrations are the top priority.

Check out other articles in the technology bites category

Discover tips on how to make better use of technology in projects

Do you have any questions?