Container Apps for microservices in Azure - Step-by-Step Execution

Process Flow - Container Apps for microservices

Create Container App Environment

↓

Deploy Microservice Container 1

→Deploy Microservice Container 2

↓

Configure Ingress & Routing

↓

Scale Microservices Automatically

↓

Monitor & Update Containers

This flow shows creating an environment, deploying multiple microservice containers, setting up routing, scaling automatically, and monitoring.

Execution Sample

Azure

az containerapp env create --name myEnv --resource-group myRG
az containerapp create --name service1 --resource-group myRG --environment myEnv --image myimage1
az containerapp create --name service2 --resource-group myRG --environment myEnv --image myimage2
az containerapp ingress enable --name service1 --resource-group myRG --environment myEnv --target-port 80
az containerapp scale set --name service1 --resource-group myRG --environment myEnv --min-replicas 1 --max-replicas 3

This code creates an environment, deploys two microservices as container apps, enables ingress on one, and sets scaling rules.

Process Table

Step	Action	Resource State	Result
1	Create Container App Environment 'myEnv'	Environment 'myEnv' created	Ready to deploy container apps
2	Deploy Container App 'service1' with image 'myimage1'	service1 deployed in 'myEnv'	Microservice 1 running
3	Deploy Container App 'service2' with image 'myimage2'	service2 deployed in 'myEnv'	Microservice 2 running
4	Enable ingress on 'service1' port 80	Ingress enabled for service1	service1 accessible via HTTP
5	Set scaling for 'service1' min=1 max=3	Scaling rules applied	service1 scales automatically between 1 and 3 replicas
6	Monitor container apps	Metrics collected	Health and performance visible
7	Update container image for 'service2'	service2 updated	New version running without downtime
8	Scale 'service1' replicas based on load	Replicas adjusted	Handles traffic spikes smoothly
9	Delete environment 'myEnv'	All container apps removed	Resources cleaned up

💡 Execution stops after environment deletion and cleanup

Status Tracker

Resource	Initial	After Step 2	After Step 3	After Step 4	After Step 5	After Step 7	Final
Environment 'myEnv'	Not created	Created	Created	Created	Created	Created	Deleted
Container App 'service1'	Not deployed	Deployed	Deployed	Ingress enabled	Scaling set	Scaling set	Deleted
Container App 'service2'	Not deployed	Not deployed	Deployed	Deployed	Deployed	Updated	Deleted
Replicas for 'service1'	0	1 (default)	1	1	1-3 (auto scale)	1-3	0

Key Moments - 3 Insights

Why do we create a Container App Environment before deploying microservices?

The environment acts like a shared space where all container apps run and communicate. Without it, container apps cannot be deployed or managed together, as shown in step 1 of the execution_table.

How does enabling ingress affect a container app?

Enabling ingress opens a network port so the app can receive external traffic. In step 4, ingress is enabled on service1, making it accessible via HTTP.

What happens when scaling rules are set for a container app?

Scaling rules let the app automatically add or remove replicas based on load. Step 5 shows setting min and max replicas, allowing the app to handle traffic changes smoothly.

Visual Quiz - 3 Questions

Look at the execution_table at step 4. What change happens to 'service1'?

A Ingress is enabled making it accessible externally

B The container image is updated

C Scaling rules are removed

D The environment is deleted

💡 Hint

Check the 'Action' and 'Result' columns at step 4 in the execution_table

According to variable_tracker, what is the state of 'service2' after step 7?

A Not deployed

B Deployed and updated

C Deleted

D Ingress enabled

💡 Hint

Look at the 'Container App service2' row under 'After Step 7' in variable_tracker

At which step does the environment get deleted?

A Step 5

B Step 7

C Step 9

D Step 3

💡 Hint

Check the last step in the execution_table and variable_tracker for environment state

Concept Snapshot

Container Apps for microservices:
- Create a Container App Environment first
- Deploy each microservice as a container app in the environment
- Enable ingress to allow external access
- Set scaling rules for automatic replica management
- Monitor and update containers without downtime
- Delete environment to clean up all resources

Full Transcript

This visual execution shows how to use Azure Container Apps to run microservices. First, you create a Container App Environment, which is a shared space for your apps. Then you deploy each microservice as a container app inside this environment. You enable ingress on apps to allow external traffic. Scaling rules help apps adjust replicas automatically based on load. You can monitor app health and update container images without downtime. Finally, deleting the environment removes all container apps and cleans up resources.