Book Image

Azure Containers Explained

By : Wesley Haakman, Richard Hooper
Book Image

Azure Containers Explained

By: Wesley Haakman, Richard Hooper

Overview of this book

Whether you’re working with a start-up or an enterprise, making decisions related to using different container technologies on Azure has a notable impact your app migration and modernization strategies. This is where companies face challenges, while choosing the right solutions and deciding when to move on to the next technology. Azure Containers Explained helps you make the right architectural choices for your solutions and get well-versed with the migration path to other platforms using practical examples. You’ll begin with a recap of containers as technology and where you can store them within Azure. Next, you’ll explore the different Microsoft Azure container technologies and understand how each platform, namely Azure Container Apps, Azure Kubernetes Service (AKS), Azure Container Instances (ACI), Azure Functions, and Azure App Services, work – you’ll learn to implement them by grasping their respective characteristics and use cases. Finally, you’ll build upon your own container solution on Azure using best practices from real-world examples and successfully transform your business from a start-up to a full-fledged enterprise. By the end of this book, you’ll be able to effectively cater to your business and application needs by selecting and modernizing your apps using various Microsoft Azure container services.
Table of Contents (22 chapters)
1
Part 1: Understanding Azure Container Technologies
8
Part 2: Choosing and Applying the Right Technology
14
Part 3: Migrating Between Technologies and Beyond

Translating features from ACI to ACA

Our next challenge is to translate the ACI configuration to ACA to make sure we can run our solution without impediments.

ACI configuration for the original use case

For ACI, we had the following configuration set up, as we discussed in Chapter 4:

  • A container group per customer
  • A billing statement API per container group
  • A public endpoint for the customer to call and request billing statements

As the use case becomes extended over time and new requirements are added, our ACA configuration may look similar, but it is, in fact, different.

ACA configuration for an extended use case

Let’s take a look at what configuration in ACA we need, according to our new use case:

  • A container app environment per customer, as this will be the “secure boundary” our customers require
  • Two container apps per environment, one for the web frontend and one for the API
  • Ingress configuration per environment...