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

Deploying and implementing the solution

Now it’s time to deploy the solution. What we need is the following:

  • ACA with vNet integration
  • Two containers (frontend and Billing API)
  • Isolation per customer (single tenancy)
  • Environment variables (Billing API address, Billing API key, and Azure SQL connection string)

You could argue that you could use much more, and that’s true. But remember: Cloud Adventures is a start-up, and we want to start small. Once we gain financial momentum, we will start making big leaps!

Important note

In the design (Figure 9.1), we are leveraging Azure SQL as a database solution. Deploying and managing Azure SQL is beyond the scope of this book. The examples provided are to show you have to pass environment variables such as connection strings to connect your solution to a database, as you will not come across many real-life scenarios that do not use any sort of database.

Let’s look at what it takes to deploy...