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

Investigating use cases for migrating between technologies

It is better to make a bad decision than to make no decision at all. Now, let’s not assume you made a bad decision and choose the wrong container platform. But if you have never made a decision, you wouldn’t have been running containers on Azure in the first place!

What we are simply trying to explain is that a container is a container, and no matter on what platform, it’s still a container. Whether you have different requirements that motivate you to move to a different container platform or because a past decision didn’t turn out so well, it does not matter. As long as we have the containers, we can talk about which platform to move them to.

We are not going to dive into each technology separately here; that is what the upcoming chapters are for. At some point in time, you have made a decision to go with a specific container technology in Azure. Let’s just say that whatever you selected...