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

Deciding the Best Fitting Azure Technologies for Multiple Containers

In the previous chapter, we went into detail on how to run a single container on Azure. There are a lot of use cases that fit those technologies but what if we are planning to use more containers?

Not all technologies on Microsoft Azure are best suited to support those workloads, and each workload could have differences in requirements, which will greatly impact the choices we have. Sometimes, it may even feel like it doesn’t matter which technology you select, but the reality can be different. In reality, it is usually more than the superficial features you see or the ballpark figure in costs you made. Sometimes, you just need to experience what is best for your solution. We will try and help you with those choices by going through a few examples and mapping them to some use cases.

In this chapter, we’re going to go over the following topics:

  • Multiple container scenarios and their solutions...