Multiple Function App with Fewer Azure Functions
  • 09 Sep 2022
  • 1 Minute to read
  • Contributors
  • Comment
  • Dark
    Light
  • PDF

Multiple Function App with Fewer Azure Functions

  • Comment
  • Dark
    Light
  • PDF

#ServerlessTips - Azure Functions
Author: Steef-Jan Wiggers Azure MVP

Azure Function App is a container for one or more functions – each interacting with other Azure Services, APIs or applications.

The function can be part of an overall serverless architecture, where components can still fail.

You do not have to worry about any infrastructure, Microsoft does that for you. However, you still need to take failure into account.

Your Function App can either run in a Consumption Plan or App Service Plan, and the issue can occur either way. Your App Service might recycle by accident – if someone decided too, or suboptimal code could be introduced through a CI/CD pipeline. Or the workload increases and the function cannot scale enough.

Consumption Plan or App Service Plan – choose the right plan

To minimize the impact to your functions, you can choose to split them up into multiple Function Apps to make them independently deployable and thus independently failable.

There is no exact rule of thumb how to split up your functions into several Function Apps – it depends on your solution architecture and requirements.

In case your functions need to communicate then you can use queues (storage or service bus queues). Furthermore, if any state is required, you can look into Durable Functions.

Azure-functions.png


Was this article helpful?