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

Pros and cons of deploying containers to Azure Functions

As with any technology and as we have seen in Chapter 2, every technology has its pros and cons.

From this chapter, you might be aware it takes quite a few steps to containerize a solution for Azure function apps. We have also learned that Azure Functions are not the technology you would initially select as the primary choice for running a container. The use case works the other way around. You are using Azure Functions but now you need to run a solution with non-standard runtimes or dependencies. If we stick to that use case, it is an acceptable solution for running containers. Let’s take a look at those pros and cons.

Pros

There are definitely a couple of reasons to use containers for Azure Functions.

It solves the problem of unsupported code and dependencies in Azure Functions

This is exactly the use case we described in the previous paragraphs. Your product manager confronts you with a piece of code...