Azure Function App running multiple instances of async code

Question

Hey there,

I have a project I'm working on that integrates Asana and DevOps.
I'm wanting to know the best practice for deploying this with the function app in regards to having multiple functions deployed to the function app.
At the moment I may have to have one instance of this project deployed to the function app per project I am wanting to integrate, I'll be using a timing trigger but I would like to know if this is the best way to solve my integration issues,

Cheers!

Answer 1

I'm wanting to know the best practice for deploying this with the function app in regards to having multiple functions deployed to the function app.

This is an interesting question and is based on a couple of things. I would suggest reading this: Function organization best practices.

At the moment I may have to have one instance of this project deployed to the function app per project I am wanting to integrate, I'll be using a timing trigger but I would like to know if this is the best way to solve my integration issues.

I am sorry, I am kind of lost here, does that mean you need to have multiple timer trigger functions in a single function app and you need to know whether it's alright? If that's your question, I see no issue with that.

Answer 2

@Bryce Mcvicar-laulau Based on what you shared, I believe you are referring to having multiple tenants of Asana and/or Azure DevOps in play. If so and if the function is expected to day the same for any tenant, it would be best to just have multiple instances of the sample function running in an infinite loop.

But this isn't straightforward to do with plain Azure Functions itself, instead leveraging Durable Functions and especially concepts like Durable Monitor and Eternal Orchestrations would be the way to go. You would start new instances and manage them as required.