Follow

Keep Up to Date with the Most Important News

By pressing the Subscribe button, you confirm that you have read and are agreeing to our Privacy Policy and Terms of Use
Contact

Is it ok to have multiple Durable functions in one function app?

I have a function application that has a time trigger function, multiple HTTP trigger functions, and 2 durable functions. Each durable function consists of a Durable Functions HTTP starter, Durable Functions orchestrator, and 2 Durable Functions activity.

While trying to debug some issues, I ran into this https://stackoverflow.com/a/69352106/7537454 post that doesn’t recommend having 2 durable functions in the same function application.

Azure documentation doesn’t have any information regarding this point. Is there any specific configuration to be done in this case?

MEDevel.com: Open-source for Healthcare and Education

Collecting and validating open-source software for healthcare, education, enterprise, development, medical imaging, medical records, and digital pathology.

Visit Medevel

It’s been 2 years since that answer was posted, and I’d appreciate if someone could provide more details.

>Solution :

You can totally have more than one orchestrator function in one Function App, no problem.

I think the answer that you linked may have misunderstood something.
They are talking about sharing the task hub, which would be an issue if you had two separate Function Apps using the same Storage account.
But even then you could just configure a different task hub name in both of those apps.

This is not an issue if it is e.g. two different orchestrator functions in one Function App.
The DurableTask runtime will route the messages it receives to the right orchestrators and activities.

Add a comment

Leave a Reply

Keep Up to Date with the Most Important News

By pressing the Subscribe button, you confirm that you have read and are agreeing to our Privacy Policy and Terms of Use

Discover more from Dev solutions

Subscribe now to keep reading and get access to the full archive.

Continue reading