Reputation: 209
I'm planning to use Azure functions to process large files and it is a long running process( > 1 hour). The file processing is triggered by queue message. The function app will be running in premium plan. As the function timeout looks same for both regular Azure function and durable functions, do I get any advantage if I chose durable functions for this long running task ?. As I'm using storage queue, the failed processing will be taken care by default after visibility time of queue message.
Also the doc says , Premium plan execution is only guaranteed for 60 minutes, but technically unbounded. Does that mean any execution over 60 minutes is not guaranteed at all ?
Upvotes: 1
Views: 1480
Reputation: 667
According to the documentation Azure Functions aren't the best fit for long-running tasks:
Azure Functions is not a recommended option for large, long-running tasks because they can cause unexpected timeout issues. However, depending on the hosting plan, they can be considered for schedule-driven triggers.
Durable Functions are used for statefull processing, with features like fan out/fan in, chaining etc.. Not sure if you get any advantage for your usecase by using them.
Upvotes: 1