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...