An Azure service that provides an event-driven serverless compute platform.
@Sampath
Yes, we are using the consumption plan, and we still wish to continue using it for this task since it is not a highly critical interactive task. However, it does take some time to analyze data in Azure Table Storage. The aim is to perform this task multiple times a day and keep the updated evaluated results ready in SQL.
Even though I mentioned that the process takes some time, its duration decreases as we run it more frequently since we are only analyzing the most recent data.
What I am trying to achieve is a mechanism to prevent the server from becoming overwhelmed. If the number of tasks exceeds the server’s capacity, there should be a buffer process to ensure that the next set of devices is not executed until the previous batches are finished. This would reduce the risk of any processes being missed.
When executing a durable function, is there an option to keep an instance in an idle state until the server is freed up before executing the next batch? My aim is to structure my code for the worst-case scenario. I am also considering whether a service bus could assist with this, assuming durable functions do not have a built-in mechanism for this natively.
Regarding maxConcurrentOrchestratorFunctions and maxConcurrentActivityFunctions, under what circumstances would we want to limit the number of active functions to 10 instead of allowing them to run at maximum capacity for scalability purposes?
From your logs, does my account show that I am using a support package?


