Discovering the Durable Functions API - Starting orchestrations (DurableOrchestrationClient part 1)
DurableOrchestrationClient(Base) class - Starting & waiting for completion
This post is the first part of a series of blogs/vlogs to discover the Durable Functions API.
In the video linked below, I'm looking into methods from the DurableOrchestrationClient(Base) class on how to start a new orchestration instance and how to retrieve the status and the result of the instance:
StartNewAsync(string orchestratorFunctionName, object input)StartNewAsync(string orchestratorFunctionName, string instanceId, object input)CreateCheckStatusResponse(HttpRequestMessage request, string instanceId)WaitForCompletionOrCreateCheckStatusResponseAsync(HttpRequestMessage request, string instanceId)WaitForCompletionOrCreateCheckStatusResponseAsync(HttpRequestMessage request, string instanceId, TimeSpan timeout)WaitForCompletionOrCreateCheckStatusResponseAsync(HttpRequestMessage request, string instanceId, TimeSpan timeout, TimeSpan retryInterval)
Here's the video, please give it a thumbs up if you like it and subscribe to my channel so you'll be notified of new videos:
Resources
- GitHub repo: github.com/marcduiker/demos-azure-durable-functions.
- Microsoft docs: Durable Functions HTTP API.
- Microsoft docs: Optional uri parameters and default values.
Links to other posts in this series
- Starting orchestrations (DurableOrchestrationClient Part 1)
- Retrieving the orchestration status (DurableOrchestrationClient Part 2)
- Purge & Terminate Orchestrations (DurableOrchestrationClient Part 3)