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.

Practice

1. What is the main purpose of scaling rules in Azure Container Apps?

easy

A. To automatically adjust the number of app instances based on demand

B. To manually restart the app when it crashes

C. To set the app's color theme

D. To limit the app's network bandwidth

Solution

1. Step 1: Understand scaling rules function

   Scaling rules help apps change the number of running instances automatically based on usage.

2. Step 2: Identify the correct purpose

   Among the options, only automatic adjustment of instances matches scaling rules' purpose.

3. Final Answer:

   To automatically adjust the number of app instances based on demand -> Option A

4. Quick Check:

   Scaling rules = auto adjust instances [OK]

Hint: Scaling rules control instance count automatically [OK]

Common Mistakes:

• Confusing scaling with manual restarts
• Thinking scaling changes app appearance
• Assuming scaling controls network limits

2. Which of the following is the correct JSON snippet to set a CPU-based scaling rule in Azure Container Apps?

easy

A. {"name":"cpu","type":"memory","metadata":{"value":"75"}}

B. {"name":"memory","type":"cpu","metadata":{"value":"75"}}

C. {"name":"cpu","type":"cpu","metadata":{"value":"75"}}

D. {"name":"requests","type":"http","metadata":{"value":"75"}}

Solution

1. Step 1: Identify correct metric type for CPU scaling

   The metric type must be "cpu" to scale based on CPU usage.

2. Step 2: Check JSON structure and metadata

   {"name":"cpu","type":"cpu","metadata":{"value":"75"}} correctly uses "cpu" type and sets a value of 75 for CPU percentage.

3. Final Answer:

   {"name":"cpu","type":"cpu","metadata":{"value":"75"}} -> Option C

4. Quick Check:

   CPU scaling JSON uses type "cpu" [OK]

Hint: CPU scaling uses type "cpu" in JSON metadata [OK]

Common Mistakes:

• Using wrong metric type like memory for CPU scaling
• Mixing HTTP request type with CPU
• Incorrect JSON key names

3. Given this scaling rule snippet:

{"name":"http","type":"http","metadata":{"concurrentRequests":"50"}}

What happens when the app receives 60 concurrent HTTP requests?

medium

A. The app scales out to add more instances

B. The app scales in to reduce instances

C. The app ignores the requests and crashes

D. The app blocks all requests above 50

Solution

1. Step 1: Understand the scaling trigger

   The rule triggers scaling when concurrent HTTP requests exceed 50.

2. Step 2: Analyze the scenario with 60 requests

   Since 60 > 50, the app will scale out by adding instances to handle load.

3. Final Answer:

   The app scales out to add more instances -> Option A

4. Quick Check:

   Requests > threshold triggers scale out [OK]

Hint: Requests above limit cause scale out [OK]

Common Mistakes:

• Thinking app scales in when load increases
• Assuming app crashes on overload
• Believing app blocks extra requests

4. You wrote this scaling rule JSON:

{"name":"cpu","type":"cpu","metadata":{"value":"abc"}}

What is the problem with this configuration?

medium

A. The JSON keys are misspelled

B. The type "cpu" is incorrect for CPU scaling

C. Scaling rules cannot use CPU metrics

D. The value for CPU threshold is not a valid number

Solution

1. Step 1: Check the value field in metadata

   The value should be a number representing CPU percentage, but "abc" is not numeric.

2. Step 2: Confirm type correctness

   The type "cpu" is correct, and keys are spelled properly.

3. Final Answer:

   The value for CPU threshold is not a valid number -> Option D

4. Quick Check:

   CPU value must be numeric [OK]

Hint: CPU threshold value must be a number [OK]

Common Mistakes:

• Using non-numeric strings for threshold values
• Changing correct type names
• Misspelling JSON keys

5. You want to configure an Azure Container App to scale between 2 and 10 instances based on CPU usage exceeding 70%. Which JSON snippet correctly sets the min and max replicas along with the CPU scaling rule?

hard

A. {"minReplicas": 10, "maxReplicas": 2, "rules": [{"name": "cpuRule", "type": "cpu", "metadata": {"value": "70"}}]}

B. {"minReplicas": 2, "maxReplicas": 10, "rules": [{"name": "cpuRule", "type": "cpu", "metadata": {"value": "70"}}]}

C. {"minReplicas": 2, "maxReplicas": 10, "rules": [{"name": "cpuRule", "type": "memory", "metadata": {"value": "70"}}]}

D. {"minReplicas": 2, "maxReplicas": 10, "rules": [{"name": "cpuRule", "type": "http", "metadata": {"concurrentRequests": "70"}}]}

Solution

1. Step 1: Verify min and max replicas values

   Min replicas should be 2 and max replicas 10 as per requirement; {"minReplicas": 2, "maxReplicas": 10, "rules": [{"name": "cpuRule", "type": "cpu", "metadata": {"value": "70"}}]} matches this correctly.

2. Step 2: Check scaling rule type and metadata

   The rule must be type "cpu" with value "70" for CPU usage threshold; {"minReplicas": 2, "maxReplicas": 10, "rules": [{"name": "cpuRule", "type": "cpu", "metadata": {"value": "70"}}]} correctly sets this.

3. Final Answer:

   {"minReplicas": 2, "maxReplicas": 10, "rules": [{"name": "cpuRule", "type": "cpu", "metadata": {"value": "70"}}]} -> Option B

4. Quick Check:

   Min/max replicas correct and CPU rule set [OK]

Hint: Min < max replicas and type "cpu" for CPU scaling [OK]

Common Mistakes:

• Swapping min and max replica values
• Using wrong metric type like memory or http
• Incorrect metadata keys for CPU scaling