Understanding Azure Durable Functions - Part 4: Passing Input To Orchestrations and Activities

added by DotNetKicks
7/31/2019 3:39:31 AM

1 Kicks, 106 Views

This is the fourth part in a series of articles. In the first part of the series we learned that Durable Functions consist of three types of function: client, orchestrator, and activity functions.Up until this point, the only data we've made use of has been hardcoded in the orchestrator function: await context.CallActivityAsync ("ReplayExample_ActivityFunction", "Tokyo"); In the preceding code, the ReplayExample_ActivityFunction is being called and the hardcoded data "Tokyo" is being passed to the activity.


0 comments