Let's take a look at how this recipe works:
- First, we developed the Orchestrator client (in our case, HttpStart), which is capable of creating Orchestrators using the StartNewAsync function of the DurableOrchestrationClient class. This method creates a new Orchestrator instance.
- Next, we developed the Orchestrator function—the most crucial part of Durable Functions. The following are a few of the most important core features of the Orchestrator context:
- It can invoke multiple activity functions
- It can save the output that's returned by an activity function and pass it to another activity function
- These Orchestrator functions are also capable of creating checkpoints that save execution points, so that if there is any problem ...