Scale Azure Functions

Question 1

Scale-out of Consumption plan

Answer 1

Event driven. Scales out automatically, even during periods of high load. Functions infrastructure scales CPU and memory resources by adding more instances based on the number of incoming trigger events.

Question 2

Consumption plan Max # instances

Answer 2

Windows: 200
Linux: 100

Question 3

Scale-out of Flex Consumption plan

Answer 3

Per-function scaling. Event-driven scaling decisions are calculated on a per-function basis, which provides a more deterministic way of scaling the functions in your app.

Question 4

Flex Consumption plan Max # instances

Answer 4

Limited only by total memory usage of all instances across a given region.

Question 5

Scale-out of Premium plan

Answer 5

Event driven. Scale out automatically based on the number of events that its functions are triggered on.

Question 6

Premium plan Max # instances

Answer 6

Windows: 100
Linux: 20-100

Question 7

Scale-out of Dedicated plan

Answer 7

Manual/autoscale

Question 8

Dedicated plan Max # instances

Answer 8

10-30
100 (ASE)

Question 9

Scale-out of Container Apps

Answer 9

Event driven. Scale out automatically by adding more instances of the Functions host, based on the number of events that its functions are triggered on.

Question 10

Container Apps Max # instances

Answer 10

10-300