When you are creating a Azure Function app, it is essential to choose between having a consumption plan and an App Service plan, based on the requirements. The following table explains the differences between these two plans:
|
Consumption plan |
App Service plan |
|
Scaling is automatically handled. Whenever there is a need for additional compute power, a consumption plan ensures that it is available. |
The function app runs on dedicated virtual machines (VMs). As such, you can scale out can by adding more VMs or enabling auto scaling. Scaling up can be achieved by choosing a different service plan. |
|
Billing is based on memory usage, the number of executions, and the amount of execution time. |
Billing is based on the number of VM instances allocated. |
|
A function cannot execute for more than 10 minutes. |
A function can run for more than 10 minutes. |
|
Not suitable for long-running Functions. |
Suitable for long-running Functions. |
|
Supports only one deployment slot. |
Supports multiple deployment slots. |
As a rule of thumb, use an App Service plan only for long-running Functions or for Functions that need more compute power than a consumption plan can provide.