In most cases, the best idea for working with functions is to keep them stateless. This makes things much easier as you do not have to worry about sharing resources and storing state. However, there are cases where you will like to access it and distribute between different instances of your functions. In such scenarios (such as orchestrating a workflow or scheduling a task to be done), a better option to start with would be to leverage the capabilities of Durable Functions, an extension to the main runtime, which changes the way you work a little bit.
It changes the way Azure Functions works as it lets you resume from where the execution was paused or stopped and introduces the possibility ...
