Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Azure Containers Explained
  • Table Of Contents Toc
  • Feedback & Rating feedback
Azure Containers Explained

Azure Containers Explained

By : Wesley Haakman , Richard Hooper
5 (1)
close
close
Azure Containers Explained

Azure Containers Explained

5 (1)
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)
close
close
1
Part 1: Understanding Azure Container Technologies
8
Part 2: Choosing and Applying the Right Technology
14
Part 3: Migrating Between Technologies and Beyond

Scalable deployments

Scalable deployments are something we hear about quite often; it might even be considered a buzzword. But it is especially very important with Kubernetes. Writing infrastructure as code to deploy solutions at scale is something we could classify as a requirement for using Kubernetes. Throughout this book, we have started with small deployments; over the course of a couple of chapters, we went from one customer to eight, and now we are preparing our infrastructure to deploy an infinite amount of customer solutions.

Doing all this the traditional way using the YAML language can become very chaotic. Normally, in YAML, we would write a file for a customer to deploy the frontend as we did in Chapter 11 (https://github.com/PacktPublishing/Azure-Containers-Explained/blob/main/CH11/frontend.yaml).

If we inspect this file, we can see some hardcoded values that ideally we would parameterize. Let’s look at the following example for an Ingress resource:

apiVersion...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY