In any durable orchestration app, the three most fundamental components are:
An activity function
An orchestrator function
A client function
Similarly, the most fundamental component of an entity app are:
An entity function
A client function
Most of the business logic resides in the activities, orchestrations, and entity functions. Most of the time, the client function is a simple function that starts the orchestration/entity and returns HTTP endpoints to query the orchestration or perform management operations. Most of the time, it would simply follow the simple HTTP example provided in the samples:
This issue is to explore the feasibility and cost-effectiveness of providing a convenience method to get rid of the client function boilerplate in the most mainstream use-cases. This could be done by, for example, providing an API that takes in an orchestration, and automatically creates and registers an HTTP client function for the user.
In any durable orchestration app, the three most fundamental components are:
Similarly, the most fundamental component of an entity app are:
Most of the business logic resides in the activities, orchestrations, and entity functions. Most of the time, the client function is a simple function that starts the orchestration/entity and returns HTTP endpoints to query the orchestration or perform management operations. Most of the time, it would simply follow the simple HTTP example provided in the samples:
This issue is to explore the feasibility and cost-effectiveness of providing a convenience method to get rid of the client function boilerplate in the most mainstream use-cases. This could be done by, for example, providing an API that takes in an orchestration, and automatically creates and registers an HTTP client function for the user.