How To Organize Azure Functions

How To Organize Azure Functions? There are multiple ways. A few key ways are as below

• Organize Azure Functions Based On Your Business Domain
• Keep the Highly used Functions in their Own Function App
• Make sure to keep the related Functions together in a Function App
• Keep the functions based on their category of usage
• Don’t Deploy different versions of Azure Functions together.
• Group the Azure Functions together based on the Trigger Event Category

Below we will discuss in detail each of the categories mentioned here.

We will discuss a very important topic, as we know the importance of Azure Functions. As part of our requirements, we will have to create many Azure Functions.

Organize Azure Functions Based On Your Business Domain

You should organize your Azure Functions Based on your Business domain requirement. We will get a better understanding if we will take an example. For example, if you will consider a travel agency. They have two departments: one is Cab booking, and another department is Support and maintenance.

The travel agency uses a set of serverless Azure functions to automate its Cab Booking Process and another set of Azure Functions to automate its support and maintenance part.

You should keep all the Azure Functions related to Cab booking in the Cab Booking Azure Function App and the Azure Functions related to support and maintenance in the Support Function App.

Keep the Highly used Functions in their Own Function App

This is another very important strategy. It means always keeping the high-use Azure functions or those with higher usage in their Azure Function Apps. If you keep a few less-used Azure functions with a high-used Azure function, then there is a chance that all the functions will scale more CPU and memory usage unnecessarily.

This is why if you keep the high-use function in its own Azure Function App, it will only scale the components that need additional resources and memory usage. This is an excellent idea. The only trick here is identifying the highly used Azure Function you can easily catch.

Make sure to keep the related Functions together in a Function App

Another idea is to keep the related Azure Functions together in an Azure Function App. Because keeping some unrelated Azure Functions together in an Azure function App is a bad idea.

Considering the consumption-based plan, as per plan, there is a very minimal difference between the scenarios where seven function apps contain a single function, and the function app contains seven functions. The charges you will get are based on the invocations of the functions.

In certain scenarios, there is a chance that both Azure Functions belong together. However, from a performance perspective, you should keep the functions in separate function apps. This is when you consider the performance of the Azure Function as the key.

Keep the functions based on their category of usage

Another strategy is that, as an organization, you will have to work with many Azure Functions, and it is quite difficult to find out if you are looking for any specific one and that one might be very similar to the others. In this scenario, if you keep the Azure functions together based on their usage category, it will be very easy for you as an organization to pool out in case you need any specific enhancements or changes.

Don’t Deploy different versions of Azure Functions together

If you are unsure about the versions of different Azure functions, don’t keep them all together inside one Azure Function App. In case of any exceptions, or if you want to add any package then it will create a lot of issues in case the versions are different.

Keeping the same versions of Azure functions together inside an Azure Function App will make maintenance and patching easier.

Group the Azure Functions together based on the Trigger Event Category

It’s a good idea to keep all the Azure Functions together based on the trigger Event category, meaning if you have some HTTP-triggered Azure functions. Then keep that HTTP-triggered Azure Functions in one Azure Function App.

This strategy will help you with easier maintenance. It will make your job easier if you want to make any code changes or perform any DNS update activities.

I personally came across this scenario, and this strategy helps you a lot and makes your task easier.

Note: It is always suggested to keep a few related Azure Functions inside the Azure Function App considering the performance and low-risk factor.

You may also like following the below Articles

• Azure Function Folder Structure
• Azure Functions Bindings
• How To Trigger Azure Functions
• Azure Function App Multiple Functions

Bijay Kumar

I am Bijay, a Microsoft MVP (10 times) having more than 17 years of experience in the software industry. During my IT career, I got a chance to share my expertise in SharePoint and Microsoft Azure, like Azure VM, Azure Active Directory, Azure PowerShell, etc. I hope you will learn from these Azure tutorials. Read more