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

ACI and the use case

Let’s first revisit the use case we built upon in Chapter 4. Based on this use case, we determined that ACI was a technical fit for us:

Your company provides an e-commerce solution to the market. Your solution is built on a number of different Microsoft Azure Technologies.

Your product manager informs you that they have purchased licensed code to help them process billing statements. This code is an extension of the existing e-commerce platform and has a number of specific characteristics. The billing statement processing is not a continuous process. The processing happens when a customer requests their billing statements, which can happen randomly at any time of day. The processing is a sort of batch process with a peak load and needs to be available on demand. Deploying infrastructure to be continuously running requires considerable resource capacity, which makes it expensive, as the billing statements are generated continuously.

Now, based on...