In this section, we will focus on deploying our containers into Microsoft Azure. This process involves some resources and services that are provided out of the box by the cloud provider. The following diagram is an overview of the architecture schema that we are going to build:

Let's take a look at the different components that are involved in this schema:

• Azure Container Registry is a managed Docker Registry service (https://docs.docker.com/registry/) based on the open source Docker Registry 2.0. It is possible to use Azure Container Registry to store, manage, and use your private Docker container images. We will use it to save images related to our custom images, such as the catalog_api image, and make them available to other cloud services.  
• The web app for containers allows us to use our containers and deploy them to App Service as a web app. Furthermore, it eliminates time-consuming infrastructure management tasks such as updating, scaling, and in general, managing the infrastructure.
• The other dependencies of the application, such as catalog_esb and catalog_cache, will take the image from the public Docker Hub (https://hub.docker.com).

Let's continue by creating an Azure Container Registry. The registry will be used further in this chapter to push and pull the image of catalog_api.