mirror of https://github.com/dapr/docs.git
add scheduleworkflow note
Signed-off-by: Cassandra Coyle <cassie@diagrid.io>
This commit is contained in:
parent
f950748584
commit
1b6ab05c6e
|
@ -292,6 +292,7 @@ func main() {
|
|||
- Use `r.AddActivity()` to register activity functions
|
||||
- Use `client.NewWorkflowClient()` to create a workflow client
|
||||
- Call `wclient.StartWorker()` to begin processing workflows
|
||||
- Use `wclient.ScheduleWorkflow` to schedule a named instance of a workflow
|
||||
|
||||
[See the Go SDK workflow activity example in context.](https://github.com/dapr/go-sdk/tree/main/examples/workflow/README.md)
|
||||
|
||||
|
|
|
@ -21,7 +21,7 @@ Some scenarios where this is useful include:
|
|||
|
||||
<img src="/images/workflow-overview/workflow-multi-app-complex.png" width=800 alt="Diagram showing multi-application complex workflow">
|
||||
|
||||
The diagram below shows an example scenario of a complex workflow that orchestrates across multiple applications that are written in different languages. Each applications' main steps and activities are;
|
||||
The diagram below shows an example scenario of a complex workflow that orchestrates across multiple applications that are written in different languages. Each applications' main steps and activities are:
|
||||
|
||||
• **App1: Main Workflow Service** - Top-level orchestrator that coordinates the entire ML pipeline
|
||||
- Starts the process
|
||||
|
|
Loading…
Reference in New Issue