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

Learnings and future decisions

AKS has grown in the past years. Where a lot of features we have been using throughout this book would traditionally require a complete redeployment of the cluster, these days, they do not. That makes Azure Kubernetes a reliable platform for an enterprise (customer) to run their containerized solutions on. Not that Kubernetes is not reliable by default, but it is very hard to explain to your customers that there is going to be downtime because you want to add a feature to your platform.

Enterprises care about governance and security and, as we stated in the introduction, if you’re starting small, you might have not thought about all of it. And if there is anything to be learned from this chapter, maintaining the quality of your AKS platform is a continuous process. All the things we have configured in the past two chapters merely scratch the surface of what you can actually do and what is to come. As long as you are willing to add or discard...