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

Decisions and the future of your solution

Will the decisions we made in the previous use case come back and haunt us? Hopefully not. But what’s important is that technologies evolve fast. Roadmaps are not set in stone and things change. This is how we concluded that we should use ACI for our use case.

We could assume containers are going to be very successful and we probably even have some insights into the company’s future that others don’t. But simply going for the platform that provides all the container capabilities we would ever need (Azure Kubernetes Service, for example) might cost us a lot of effort in terms of training developers, expensive infrastructure, and one or two sleepless nights to get it done.

Small steps will eventually become huge leaps. We have just made a small step by introducing container technology to our developers but with minimum requirements. They can still write code as they are used to, and we will help them create that Dockerfile...