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

The next technology

We are just throwing it in there: the next technology we migrate to might very well end up being AKS! Yes, we can run everything on Azure Container Instances and ACA and it will run, but it won’t be the most efficient.

Let us take a look at the new facts:

  • The web frontend relies on the billing statement API.
  • The solution (frontend and API) is deployed per customer (single tenant).
  • The solution runs 24/7 throughout the month.
  • We need to service 25 customers (new requirement).
  • We need a custom domain for each customer.
  • The billing API and the web frontend have different life cycles.
  • The billing API can generate a peak workload, therefore we need scaling.
  • New additions to the platform will be containerized (new requirement).

Even though there are only two new requirements, they make all the difference. As mentioned before, 25 customers mean at least 50 containers. New services (if deployed for each customer) cause...