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

Summary

In this chapter, we have learned that growth in your business can mean a change in technology. It’s really about how you plan for this and even whether you can accept it. A decision you made a year ago can very well need to be revisited – accept that. Look at it like this – the fact that you had to revisit this decision means your company is doing well. There is no shame in that!

We have seen that out-of-the-box technologies are fine until you have to deal with specific requirements. Once that happens, the answer is almost always AKS – not just because we love AKS but because it also provides flexibility. And if we really just go by the requirements, it is not that difficult to use. When it comes to using Kubernetes, it only becomes difficult when you want to go from 0–100. Just use what you need.

In the next chapter, we will look at an enterprise scenario. What about scaling? What about management and monitoring? There is no single...