Using the App Service model has its benefits, especially when it comes to covering some cases of scaling that are not covered in the consumption plan. As mentioned in the previous section, if you have to be sure that you are able to handle the incoming load, it is often a better idea to use this particular model, as it ensures that some fixed resources will be available for your function app. Additionally, you are 100% sure that the provided hardware is provisioned for your application—this is not always the case in the consumption model since you have no guarantees when it comes to delivered machines and their characteristics. What's more, you are sure that your runtime is always running—since, in the consumption ...
Scaling in the App Service model
Get Hands-On Azure for Developers now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
