Container Apps scaling rules in Azure - Step-by-Step Execution

Process Flow - Container Apps scaling rules

App receives traffic/load

↓

Monitor metrics (CPU, HTTP requests, etc.)

↓

Evaluate scaling rules

↓

Scale Out

↓

Add container

↓

App adjusts container count

↓

Repeat monitoring

The app watches its load, checks rules, then adds or removes containers to handle traffic smoothly.

Execution Sample

Azure

scaleRule:
  name: http-scaler
  type: http
  metadata:
    concurrentRequests: '50'

This rule scales out when concurrent HTTP requests exceed 50, and scales in when below.

Process Table

Step	Metric Observed	Current Containers	Rule Evaluated	Action Taken	New Container Count
1	40 concurrent requests	2	Requests < 50	No scaling	2
2	55 concurrent requests	2	Requests > 50	Scale out	3
3	70 concurrent requests	3	Requests > 50	Scale out	4
4	45 concurrent requests	4	Requests < 50	Scale in	3
5	30 concurrent requests	3	Requests < 50	Scale in	2
6	25 concurrent requests	2	Requests < 50	No scaling	2

💡 Load stabilizes below threshold, no further scaling needed.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6
concurrentRequests	0	40	55	70	45	30	25
containerCount	2	2	3	4	3	2	2

Key Moments - 3 Insights

Why does the container count increase when requests go from 40 to 55?

Because the scaling rule triggers when concurrent requests exceed 50, as shown in step 2 of the execution_table.

Why does the container count decrease when requests drop from 70 to 45?

The rule scales in when requests fall below 50, so at step 4 the container count reduces from 4 to 3.

Why is there no scaling at step 6 even though requests are 25?

Because the container count is already at minimum needed (2), so no further scale-in happens as per the rule.

Visual Quiz - 3 Questions

Look at the execution_table, what is the container count after step 3?

A 4

B 3

C 2

D 5

💡 Hint

Check the 'New Container Count' column at step 3 in the execution_table.

At which step does the scaling rule first trigger a scale out?

A Step 1

B Step 4

C Step 2

D Step 5

💡 Hint

Look for the first 'Scale out' action in the 'Action Taken' column.

If the concurrentRequests threshold was changed to 60, what would happen at step 3?

A Scale out to 4 containers

B No scaling, remain at 3 containers

C Scale in to 2 containers

D Scale out to 5 containers

💡 Hint

Compare the 'Metric Observed' at step 3 with the new threshold and check the 'Rule Evaluated' logic.

Concept Snapshot

Container Apps scaling rules watch app load metrics.
If load exceeds thresholds, containers are added (scale out).
If load drops below thresholds, containers are removed (scale in).
Rules use metrics like CPU, HTTP requests.
This keeps app responsive and cost-efficient.

Full Transcript

Container Apps scaling rules work by monitoring app load metrics such as concurrent HTTP requests. When the load goes above a set threshold, the app adds containers to handle the extra traffic, called scaling out. When the load drops below the threshold, it removes containers, called scaling in. This process repeats continuously to keep the app responsive without wasting resources. For example, if the rule triggers at 50 concurrent requests, the app will add containers when requests go above 50 and remove them when below. The execution table shows how container count changes step by step as load varies. This helps beginners see how scaling decisions happen in real time.