Durable Functions are long-running, serverless functions with a stateful architecture. They are used where the duration between function calls vary.
An example of durable function architecture is a file upload system with admin verification. If we want to upload some files to Azure Blob Storage and then have an admin verify valid files, we could make use of Durable Functions. The admin verification process could span over a couple of days or a few minutes. After the verification is complete, another function that compresses the valid files could run.
Client functions are the standard Azure Functions that serve as the entry point of a durable function workflow. These client functions run in response to triggers such as HTTP, Blob Storage, and Timer.
Orchestrator functions describe how durable function workflow actions are executed.
Entity functions define operations for modifying and reading small pieces of state. Much like Orchestrator function types, entity functions have
Activity functions are the actions that are executed by the durable function workflow. An activity is the basic unit of work that contains executable code.
View all Courses