diff --git a/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-architecture.md b/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-architecture.md index 87c90ca14bc..78d845150cf 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-architecture.md +++ b/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-architecture.md @@ -31,7 +31,7 @@ When a workflow application starts up, it uses a workflow authoring SDK to send The workflow app executes the appropriate workflow code and then sends a gRPC request back to the sidecar with the execution results. -Dapr Workflow Engine Protocol +Dapr Workflow Engine Protocol All interactions happen over a single gRPC channel and are initiated by the application, which means the application doesn't need to open any inbound ports. The details of these interactions are internally handled by the language-specific Dapr Workflow authoring SDK. @@ -91,7 +91,7 @@ Workflow actor state remains in the state store even after a workflow has comple The following diagram illustrates the typical lifecycle of a workflow actor. -Dapr Workflow Actor Flowchart +Dapr Workflow Actor Flowchart To summarize: @@ -113,7 +113,7 @@ Each activity actor stores a single key into the state store: The following diagram illustrates the typical lifecycle of an activity actor. -Workflow Activity Actor Flowchart +Workflow Activity Actor Flowchart Activity actors are short-lived: diff --git a/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-patterns.md b/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-patterns.md index 24db5b49252..ee59dd1d390 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-patterns.md +++ b/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-patterns.md @@ -710,7 +710,7 @@ The monitor pattern is recurring process that typically: The following diagram provides a rough illustration of this pattern. -Diagram showing how the monitor pattern works +Diagram showing how the monitor pattern works Depending on the business needs, there may be a single monitor or there may be multiple monitors, one for each business entity (for example, a stock). Furthermore, the amount of time to sleep may need to change, depending on the circumstances. These requirements make using cron-based scheduling systems impractical. @@ -953,7 +953,7 @@ Here's an example workflow for a purchase order involving a human: The following diagram illustrates this flow. -Diagram showing how the external system interaction pattern works with a human involved +Diagram showing how the external system interaction pattern works with a human involved The following example code shows how this pattern can be implemented using Dapr Workflow. diff --git a/daprdocs/static/images/workflow-overview/workflow-activity-actor-flowchart.png b/daprdocs/static/images/workflow-overview/workflow-activity-actor-flowchart.png index db626764e9b..e2a758c6ce1 100644 Binary files a/daprdocs/static/images/workflow-overview/workflow-activity-actor-flowchart.png and b/daprdocs/static/images/workflow-overview/workflow-activity-actor-flowchart.png differ diff --git a/daprdocs/static/images/workflow-overview/workflow-actor-flowchart.png b/daprdocs/static/images/workflow-overview/workflow-actor-flowchart.png index 93122809f70..08c62b19e5c 100644 Binary files a/daprdocs/static/images/workflow-overview/workflow-actor-flowchart.png and b/daprdocs/static/images/workflow-overview/workflow-actor-flowchart.png differ diff --git a/daprdocs/static/images/workflow-overview/workflow-actor-reminder-flow.png b/daprdocs/static/images/workflow-overview/workflow-actor-reminder-flow.png index 06896d26233..59c5e34b8b4 100644 Binary files a/daprdocs/static/images/workflow-overview/workflow-actor-reminder-flow.png and b/daprdocs/static/images/workflow-overview/workflow-actor-reminder-flow.png differ diff --git a/daprdocs/static/images/workflow-overview/workflow-actor-scale-out.png b/daprdocs/static/images/workflow-overview/workflow-actor-scale-out.png index d3c83441e59..ef9eee73513 100644 Binary files a/daprdocs/static/images/workflow-overview/workflow-actor-scale-out.png and b/daprdocs/static/images/workflow-overview/workflow-actor-scale-out.png differ diff --git a/daprdocs/static/images/workflow-overview/workflow-async-request-response.png b/daprdocs/static/images/workflow-overview/workflow-async-request-response.png index 672ef3afe75..60f1aa362c1 100644 Binary files a/daprdocs/static/images/workflow-overview/workflow-async-request-response.png and b/daprdocs/static/images/workflow-overview/workflow-async-request-response.png differ diff --git a/daprdocs/static/images/workflow-overview/workflow-engine-protocol.png b/daprdocs/static/images/workflow-overview/workflow-engine-protocol.png index 2a2ff09327d..3921c6b9e0a 100644 Binary files a/daprdocs/static/images/workflow-overview/workflow-engine-protocol.png and b/daprdocs/static/images/workflow-overview/workflow-engine-protocol.png differ diff --git a/daprdocs/static/images/workflow-overview/workflow-execution.png b/daprdocs/static/images/workflow-overview/workflow-execution.png index bf5a9244e1b..541d6539302 100644 Binary files a/daprdocs/static/images/workflow-overview/workflow-execution.png and b/daprdocs/static/images/workflow-overview/workflow-execution.png differ diff --git a/daprdocs/static/images/workflow-overview/workflow-human-interaction-pattern.png b/daprdocs/static/images/workflow-overview/workflow-human-interaction-pattern.png index 4bd97cd95d5..3c552614b3c 100644 Binary files a/daprdocs/static/images/workflow-overview/workflow-human-interaction-pattern.png and b/daprdocs/static/images/workflow-overview/workflow-human-interaction-pattern.png differ diff --git a/daprdocs/static/images/workflow-overview/workflow-monitor-pattern.png b/daprdocs/static/images/workflow-overview/workflow-monitor-pattern.png index e61dc30aa21..2761f3e4b1d 100644 Binary files a/daprdocs/static/images/workflow-overview/workflow-monitor-pattern.png and b/daprdocs/static/images/workflow-overview/workflow-monitor-pattern.png differ diff --git a/daprdocs/static/images/workflow-overview/workflow-overview.png b/daprdocs/static/images/workflow-overview/workflow-overview.png index cace4612261..e534f4e822b 100644 Binary files a/daprdocs/static/images/workflow-overview/workflow-overview.png and b/daprdocs/static/images/workflow-overview/workflow-overview.png differ diff --git a/daprdocs/static/images/workflow-overview/workflow-state-store-interactions.png b/daprdocs/static/images/workflow-overview/workflow-state-store-interactions.png index 270fda53760..09be4b3446d 100644 Binary files a/daprdocs/static/images/workflow-overview/workflow-state-store-interactions.png and b/daprdocs/static/images/workflow-overview/workflow-state-store-interactions.png differ diff --git a/daprdocs/static/images/workflow-overview/workflows-architecture-k8s.png b/daprdocs/static/images/workflow-overview/workflows-architecture-k8s.png index 394891e0563..d005e80ee1b 100644 Binary files a/daprdocs/static/images/workflow-overview/workflows-architecture-k8s.png and b/daprdocs/static/images/workflow-overview/workflows-architecture-k8s.png differ diff --git a/daprdocs/static/images/workflow-overview/workflows-chaining.png b/daprdocs/static/images/workflow-overview/workflows-chaining.png index 7ab8ebcef9b..5238ec88b42 100644 Binary files a/daprdocs/static/images/workflow-overview/workflows-chaining.png and b/daprdocs/static/images/workflow-overview/workflows-chaining.png differ diff --git a/daprdocs/static/images/workflow-overview/workflows-fanin-fanout.png b/daprdocs/static/images/workflow-overview/workflows-fanin-fanout.png index 6fa4db295c3..8723c270300 100644 Binary files a/daprdocs/static/images/workflow-overview/workflows-fanin-fanout.png and b/daprdocs/static/images/workflow-overview/workflows-fanin-fanout.png differ