This is an automated email from the ASF dual-hosted git repository.
mikexue pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/eventmesh-site.git
The following commit(s) were added to refs/heads/master by this push:
new e402590da [ISSUE #189] Transcribe Serverless Workflow Demo Runbook
(#190)
e402590da is described below
commit e402590da48827f5fac07a9bfe0a2112c90c064d
Author: Pil0tXia <[email protected]>
AuthorDate: Mon Jan 29 10:06:07 2024 +0800
[ISSUE #189] Transcribe Serverless Workflow Demo Runbook (#190)
* Add workflow-demo CN/EN docs
* Move workflow-* images to /workflow
---
.../06-workflow.md | 6 +-
docs/instruction/07-workflow-demo.md | 205 +++++++++++++++++++++
docs/instruction/{07-faq.md => 08-faq.md} | 0
.../06-workflow.md | 7 +-
.../current/instruction/07-workflow-demo.md | 201 ++++++++++++++++++++
.../current/instruction/{07-faq.md => 08-faq.md} | 0
.../06-workflow.md | 7 +-
.../version-v1.7.0/design-document/01-workflow.md | 6 +-
.../06-workflow.md | 7 +-
.../06-workflow.md | 7 +-
.../{ => workflow}/workflow-architecture.jpg | Bin
.../design-document/workflow/workflow-demo-1.png | Bin 0 -> 53757 bytes
.../design-document/workflow/workflow-demo-2.png | Bin 0 -> 85865 bytes
.../design-document/workflow/workflow-demo-3.png | Bin 0 -> 29068 bytes
.../design-document/workflow/workflow-demo-4.png | Bin 0 -> 74472 bytes
.../{ => workflow}/workflow-diagram.png | Bin
.../{ => workflow}/workflow-use-case.jpg | Bin
.../06-workflow.md | 6 +-
.../version-v1.7.0/design-document/01-workflow.md | 6 +-
.../06-workflow.md | 6 +-
.../06-workflow.md | 6 +-
21 files changed, 436 insertions(+), 34 deletions(-)
diff --git
a/docs/design-document/01-event-handling-and-integration/06-workflow.md
b/docs/design-document/01-event-handling-and-integration/06-workflow.md
index eff287bad..76dd8b773 100644
--- a/docs/design-document/01-event-handling-and-integration/06-workflow.md
+++ b/docs/design-document/01-event-handling-and-integration/06-workflow.md
@@ -6,7 +6,7 @@ Imaging you are building a simple Order Management System for
an E-Commerce Stor
For high availability and high performance, you architect the system using
event-driven architecture (EDA), and build microservice apps to handle store
frontend, order management, payment processing, and shipment management. You
deploy the whole system in a cloud environment. To handle high workloads, you
leverage a messaging system to buffer the loads, and scale up multiple
instances of microservices. The architecture could look similar to:
-
+
While each microservice is acting on its own event channels, EventMesh plays a
crucial role of doing Event Orchestration.
@@ -181,13 +181,13 @@ events:
The corresponding workflow diagram is the following:
-
+
## EventMesh Workflow Engine
In the following architecture diagram, the EventMesh Catalog, EventMesh
Workflow Engine and EventMesh Runtime are running in three different processors.
-
+
The steps running the workflow is the followings:
diff --git a/docs/instruction/07-workflow-demo.md
b/docs/instruction/07-workflow-demo.md
new file mode 100644
index 000000000..523bae5a3
--- /dev/null
+++ b/docs/instruction/07-workflow-demo.md
@@ -0,0 +1,205 @@
+# Run Serverless Workflow Demo
+
+## 1. Environment Requirements
+
+The current Runbook is based on the all-in-one approach, and this document is
also based on that premise.
+
+1. MySQL 8.0+
+
+2. Nacos latest version is sufficient
+
+3. EventMesh-Server
+
+Note: Change connector-type to standalone
+
+All three services mentioned above need to be started in advance.
+
+## 2. Initialize Database
+
+### Initialize workflow database
+
+ ```shell
+ cd eventmesh-workflow-go/distribution
+ mysql -h mysql_host -u mysql_user -p mysql_password < ./mysql-schema.sql
+ ```
+
+### Initialize catalog database
+
+ ```shell
+ cd eventmesh-catalog-go/distribution
+ mysql -h mysql_host -u mysql_user -p mysql_password < ./mysql-schema.sql
+ ```
+
+## 3. Import Workflow Demo Data
+
+### Import eventmesh-workflow db data
+
+- Workflow basic information: t_workflow
+- Workflow task information: t_workflow_task
+- Workflow task execution information: t_worklfow_task_action
+- Workflow task relation information: t_wofkflow_task_relation
+
+```shell
+cd eventmesh-workflow-go/cmd
+bash build.sh
+./workflow-cli create --file ../configs/testcreateworkflow.yaml --dsn
"root:123456@(127.0.0.1:3306)/db_workflow?charset=utf8&parseTime=True&loc=Local"
+```
+
+### Import eventmesh-catalog db data
+
+```shell
+cd eventmesh-catalog-go/cmd
+bash build.sh
+./catalog-cli create --file ../configs/testorder.yaml --dsn
"root:123456@(127.0.0.1:3306)/db_catalog?charset=utf8&parseTime=True&loc=Local"
+./catalog-cli create --file ../configs/testpayment.yaml --dsn
"root:123456@(127.0.0.1:3306)/db_catalog?charset=utf8&parseTime=True&loc=Local"
+./catalog-cli create --file ../configs/testexpress.yaml --dsn
"root:123456@(127.0.0.1:3306)/db_catalog?charset=utf8&parseTime=True&loc=Local"
+```
+
+## 4. Run Workflow Services
+
+### Run eventmesh-workflow service
+
+Modify the service's runtime configuration file `./configs/workflow.yaml`
+
+```yml
+server:
+ port: 11012
+ name: "EVENTMESH-workflow"
+flow:
+ queue:
+ store: in-memory
+ scheduler:
+ type: in-line
+ interval: 10 # milliseconds
+ protocol: meshmessage
+catalog:
+ server_name: "EVENTMESH-catalog"
+eventmesh:
+ host: "127.0.0.1"
+ env: "PRD"
+ idc: "DEFAULT"
+ sys: "DEFAULT"
+ username: "username"
+ password: "password"
+ producer_group: "EventMeshTest-producerGroup"
+ ttl: 4000
+ grpc:
+ port: 10205
+plugins:
+ registry:
+ nacos:
+ address_list: "127.0.0.1:8848"
+ selector:
+ nacos:
+ address_list: "127.0.0.1:8848"
+ database:
+ mysql:
+ dsn:
"root:123456@(127.0.0.1:3306)/db_workflow?charset=utf8&parseTime=True&loc=Local"
+ max_idle: 50
+ max_open: 100
+ max_lifetime: 180000
+ log:
+ default:
+ - writer: file
+ level: info
+ writer_config:
+ filename: ./workflow.log
+ max_size: 10
+ max_backups: 10
+ max_age: 7
+ compress: false
+ schedule:
+ - writer: file
+ level: info
+ writer_config:
+ filename: ./workflow_schedule.log
+ max_size: 10
+ max_backups: 10
+ max_age: 7
+ compress: false
+ queue:
+ - writer: file
+ level: info
+ writer_config:
+ filename: ./workflow_queue.log
+ max_size: 10
+ max_backups: 10
+ max_age: 7
+ compress: false
+```
+
+Run the service: (Can also be directly run in GoLand using main)
+
+```shell
+go build
+./eventmesh-workflow-go
+```
+
+Notes:
+
+ - Eventmesh configuration needs to correspond to eventmsh-server
configuration.
+
+ ```yml
+ eventmesh:
+ host: "127.0.0.1"
+ env: "PRD"
+ idc: "DEFAULT"
+ sys: "DEFAULT"
+ username: "username"
+ password: "password"
+ producer_group: "EventMeshTest-producerGroup"
+ ttl: 4000
+ grpc:
+ port: 10205
+ ```
+
+ - Nacos address needs to be modified.
+
+ - MySQL DSN needs to be modified.
+
+### Run eventmesh-catalog service
+
+Modify the configuration file `./configs/catalog.yaml`, similar points to the
workflow service.
+
+Run the service: (Can also be directly run in GoLand using main)
+
+```shell
+go build
+./eventmesh-catalog-go
+```
+
+## 5. Run Workflow Demo Pub/Sub Application
+
+It is necessary to start the pub/sub application after the successful run of
eventmesh-workflow/eventmesh-catalog services.
+
+### Pub application
+
+WorkflowAsyncPublishInstance
+
+1. This configuration needs to correspond to EventMesh-Server.
+
+
+
+2. Workflowid needs to correspond to the imported data.
+
+
+
+### Sub application
+
+WorkflowOrderAsyncSubscribe
+
+WorkflowPaymentAsyncSubscribe
+
+WorkflowExpressAsyncSubscribe
+
+Note: workflowid needs to correspond to the imported data.
+
+Run results:
+
+- t_workflow_instance: Status 2, run completed.
+
+
+
+- t_workflow_task_instance: All tasks in the process have status 4, run
successful.
+
+
\ No newline at end of file
diff --git a/docs/instruction/07-faq.md b/docs/instruction/08-faq.md
similarity index 100%
rename from docs/instruction/07-faq.md
rename to docs/instruction/08-faq.md
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/current/design-document/01-event-handling-and-integration/06-workflow.md
b/i18n/zh/docusaurus-plugin-content-docs/current/design-document/01-event-handling-and-integration/06-workflow.md
index 19d130241..daf161f12 100644
---
a/i18n/zh/docusaurus-plugin-content-docs/current/design-document/01-event-handling-and-integration/06-workflow.md
+++
b/i18n/zh/docusaurus-plugin-content-docs/current/design-document/01-event-handling-and-integration/06-workflow.md
@@ -6,7 +6,7 @@
为了实现高可用和高性能，你可以使用事件驱动架构（EDA）构建微服务应用去处理商店前端，订单管理，支付处理和发货管理。你可以在云上部署整个系统。要处理高并发，你可以利用消息系统缓冲，并扩展多个微服务实例。架构类似于：
-
+
当每个微服务都在自己的事件通道上运行时，EventMesh 在执行事件编排方面发挥着至关重要的作用。
@@ -178,13 +178,13 @@ events:
对应的工作流图如下：
-
+
## EventMesh 工作流引擎
在下面的体系结构图中，EventMesh 目录，EventMesh 工作流引擎 和 EventMesh Runtime 在三个不同的处理器中运行。
-
+
运行工作流的步骤如下：
@@ -256,4 +256,3 @@ EventMesh 目录存储发布者、订阅者和通道元数据。由以下模块
- 重试模块
管理事件发布到 EventMesh Runtime 的重试逻辑。
-
\ No newline at end of file
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/current/instruction/07-workflow-demo.md
b/i18n/zh/docusaurus-plugin-content-docs/current/instruction/07-workflow-demo.md
new file mode 100644
index 000000000..8431c9e8b
--- /dev/null
+++
b/i18n/zh/docusaurus-plugin-content-docs/current/instruction/07-workflow-demo.md
@@ -0,0 +1,201 @@
+# 运行 Serverless Workflow Demo
+
+## 1. 环境要求
+
+当前 Runbook 基于单机 (all-in-one) 方式，本文档也是基于该前提。
+
+1. MySQL 8.0+
+2. Nacos 最新版本即可
+3. EventMesh-Server
+
+注意：connector-type 需要修改为 standalone
+
+以上三个服务需要提前运行起来。
+
+## 2. 初始化数据库
+
+### 初始化 workflow 数据库
+
+```shell
+cd eventmesh-workflow-go/distribution
+mysql -h mysql_host -u mysql_user -p mysql_password < ./mysql-schema.sql
+```
+
+### 初始化 catalog 数据库
+
+```shell
+cd eventmesh-catalog-go/distribution
+mysql -h mysql_host -u mysql_user -p mysql_password < ./mysql-schema.sql
+```
+
+## 3. 导入工作流演示数据
+
+### 导入 eventmesh-workflow 数据库数据
+
+- 工作流基础信息：t_workflow
+- 工作流任务信息：t_workflow_task
+- 工作流任务执行信息：t_worklfow_task_action
+- 工作流任务关系信息：t_wofkflow_task_relation
+
+```shell
+cd eventmesh-workflow-go/cmd
+bash build.sh
+./workflow-cli create --file ../configs/testcreateworkflow.yaml --dsn
"root:123456@(127.0.0.1:3306)/db_workflow?charset=utf8&parseTime=True&loc=Local"
+```
+
+### 导入 eventmesh-catalog 数据库数据
+
+```shell
+cd eventmesh-catalog-go/cmd
+bash build.sh
+./catalog-cli create --file ../configs/testorder.yaml --dsn
"root:123456@(127.0.0.1:3306)/db_catalog?charset=utf8&parseTime=True&loc=Local"
+./catalog-cli create --file ../configs/testpayment.yaml --dsn
"root:123456@(127.0.0.1:3306)/db_catalog?charset=utf8&parseTime=True&loc=Local"
+./catalog-cli create --file ../configs/testexpress.yaml --dsn
"root:123456@(127.0.0.1:3306)/db_catalog?charset=utf8&parseTime=True&loc=Local"
+```
+
+## 4. 运行工作流服务
+
+### 运行 eventmesh-workflow 服务
+
+修改服务运行配置文件 `./configs/workflow.yaml`
+
+```yml
+server:
+port: 11012
+name: "EVENTMESH-workflow"
+flow:
+queue:
+ store: in-memory
+scheduler:
+ type: in-line
+ interval: 10 # milliseconds
+protocol: meshmessage
+catalog:
+server_name: "EVENTMESH-catalog"
+eventmesh:
+host: "127.0.0.1"
+env: "PRD"
+idc: "DEFAULT"
+sys: "DEFAULT"
+username: "username"
+password: "password"
+producer_group: "EventMeshTest-producerGroup"
+ttl: 4000
+grpc:
+ port: 10205
+plugins:
+registry:
+ nacos:
+ address_list: "127.0.0.1:8848"
+selector:
+ nacos:
+ address_list: "127.0.0.1:8848"
+database:
+ mysql:
+ dsn:
"root:123456@(127.0.0.1:3306)/db_workflow?charset=utf8&parseTime=True&loc=Local"
+ max_idle: 50
+ max_open: 100
+ max_lifetime: 180000
+log:
+ default:
+ - writer: file
+ level: info
+ writer_config:
+ filename: ./workflow.log
+ max_size: 10
+ max_backups: 10
+ max_age: 7
+ compress: false
+ schedule:
+ - writer: file
+ level: info
+ writer_config:
+ filename: ./workflow_schedule.log
+ max_size: 10
+ max_backups: 10
+ max_age: 7
+ compress: false
+ queue:
+ - writer: file
+ level: info
+ writer_config:
+ filename: ./workflow_queue.log
+ max_size: 10
+ max_backups: 10
+ max_age: 7
+ compress: false
+```
+
+运行服务： （也可以直接在 GoLand 直接运行 main）
+
+```shell
+go build
+./eventmesh-workflow-go
+```
+
+注意：
+- Eventmesh 配置需要和 eventmsh-server 的配置一一对应。
+
+ ```yml
+ eventmesh:
+ host: "127.0.0.1"
+ env: "PRD"
+ idc: "DEFAULT"
+ sys: "DEFAULT"
+ username: "username"
+ password: "password"
+ producer_group: "EventMeshTest-producerGroup"
+ ttl: 4000
+ grpc:
+ port: 10205
+ ```
+
+- Nacos 地址需要修改。
+
+- MySQL DSN 需要修改。
+
+### 运行 eventmesh-catalog 服务
+
+修改配置文件 `./configs/catalog.yaml`，相关注意点同 workflow 服务。
+
+运行服务： （也可以直接在 GoLand 直接运行 main）
+
+```shell
+go build
+./eventmesh-catalog-go
+```
+
+## 5. 运行工作流演示 Pub/Sub 应用
+
+需要在 eventmesh-workflow/eventmesh-catalog 服务运行成功后再启动 pub/sub 应用。
+
+### Pub 应用
+
+WorkflowAsyncPublishInstance
+
+1. 这个配置需要和 EventMesh-Server 一一对应。
+
+
+
+1. Workflowid 需要和导入的数据一一对应上。
+
+
+
+### Sub 应用
+
+WorkflowOrderAsyncSubscribe
+
+WorkflowPaymentAsyncSubscribe
+
+WorkflowExpressAsyncSubscribe
+
+注意：workflowid 需要和导入的数据一一对应上。
+
+运行结果：
+- t_workflow_instance: 状态为 2，运行结束。
+
+
+
+- t_workflow_task_instance: 流程所有任务状态为 4，运行成功。
+
+
\ No newline at end of file
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/current/instruction/07-faq.md
b/i18n/zh/docusaurus-plugin-content-docs/current/instruction/08-faq.md
similarity index 100%
rename from i18n/zh/docusaurus-plugin-content-docs/current/instruction/07-faq.md
rename to i18n/zh/docusaurus-plugin-content-docs/current/instruction/08-faq.md
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.10.0/design-document/01-event-handling-and-integration/06-workflow.md
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.10.0/design-document/01-event-handling-and-integration/06-workflow.md
index 19d130241..daf161f12 100644
---
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.10.0/design-document/01-event-handling-and-integration/06-workflow.md
+++
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.10.0/design-document/01-event-handling-and-integration/06-workflow.md
@@ -6,7 +6,7 @@
为了实现高可用和高性能，你可以使用事件驱动架构（EDA）构建微服务应用去处理商店前端，订单管理，支付处理和发货管理。你可以在云上部署整个系统。要处理高并发，你可以利用消息系统缓冲，并扩展多个微服务实例。架构类似于：
-
+
当每个微服务都在自己的事件通道上运行时，EventMesh 在执行事件编排方面发挥着至关重要的作用。
@@ -178,13 +178,13 @@ events:
对应的工作流图如下：
-
+
## EventMesh 工作流引擎
在下面的体系结构图中，EventMesh 目录，EventMesh 工作流引擎 和 EventMesh Runtime 在三个不同的处理器中运行。
-
+
运行工作流的步骤如下：
@@ -256,4 +256,3 @@ EventMesh 目录存储发布者、订阅者和通道元数据。由以下模块
- 重试模块
管理事件发布到 EventMesh Runtime 的重试逻辑。
-
\ No newline at end of file
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.7.0/design-document/01-workflow.md
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.7.0/design-document/01-workflow.md
index bed1a7fc2..a0043fab3 100644
---
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.7.0/design-document/01-workflow.md
+++
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.7.0/design-document/01-workflow.md
@@ -6,7 +6,7 @@
为了实现高可用和高性能，你可以使用事件驱动架构（EDA）构建微服务应用去处理商店前端，订单管理，支付处理和发货管理。你可以在云上部署整个系统。要处理高并发，你可以利用消息系统缓冲，并扩展多个微服务实例。架构类似于：
-
+
当每个微服务都在自己的事件通道上运行时，EventMesh在执行事件编排方面发挥着至关重要的作用。
@@ -178,13 +178,13 @@ events:
对应的工作流图如下：
-
+
## EventMesh工作流引擎
在下面的体系结构图中, EventMesh目录, EventMesh工作流引擎 和 EventMesh Runtime在三个不同的处理器中运行。
-
+
运行工作流的步骤如下：
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.8.0/design-document/01-event-handling-and-integration/06-workflow.md
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.8.0/design-document/01-event-handling-and-integration/06-workflow.md
index 0eb2cc8a2..ca0ce9c47 100644
---
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.8.0/design-document/01-event-handling-and-integration/06-workflow.md
+++
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.8.0/design-document/01-event-handling-and-integration/06-workflow.md
@@ -6,7 +6,7 @@
为了实现高可用和高性能，你可以使用事件驱动架构（EDA）构建微服务应用去处理商店前端，订单管理，支付处理和发货管理。你可以在云上部署整个系统。要处理高并发，你可以利用消息系统缓冲，并扩展多个微服务实例。架构类似于：
-
+
当每个微服务都在自己的事件通道上运行时，EventMesh在执行事件编排方面发挥着至关重要的作用。
@@ -178,13 +178,13 @@ events:
对应的工作流图如下：
-
+
## EventMesh工作流引擎
在下面的体系结构图中, EventMesh目录, EventMesh工作流引擎 和 EventMesh Runtime在三个不同的处理器中运行。
-
+
运行工作流的步骤如下：
@@ -256,4 +256,3 @@ EventMesh目录存储发布者、订阅者和通道元数据。由以下模块
- 重试模块
管理事件发布到EventMesh Runtime的重试逻辑。
-
\ No newline at end of file
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.9.0/design-document/01-event-handling-and-integration/06-workflow.md
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.9.0/design-document/01-event-handling-and-integration/06-workflow.md
index 0eb2cc8a2..ca0ce9c47 100644
---
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.9.0/design-document/01-event-handling-and-integration/06-workflow.md
+++
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.9.0/design-document/01-event-handling-and-integration/06-workflow.md
@@ -6,7 +6,7 @@
为了实现高可用和高性能，你可以使用事件驱动架构（EDA）构建微服务应用去处理商店前端，订单管理，支付处理和发货管理。你可以在云上部署整个系统。要处理高并发，你可以利用消息系统缓冲，并扩展多个微服务实例。架构类似于：
-
+
当每个微服务都在自己的事件通道上运行时，EventMesh在执行事件编排方面发挥着至关重要的作用。
@@ -178,13 +178,13 @@ events:
对应的工作流图如下：
-
+
## EventMesh工作流引擎
在下面的体系结构图中, EventMesh目录, EventMesh工作流引擎 和 EventMesh Runtime在三个不同的处理器中运行。
-
+
运行工作流的步骤如下：
@@ -256,4 +256,3 @@ EventMesh目录存储发布者、订阅者和通道元数据。由以下模块
- 重试模块
管理事件发布到EventMesh Runtime的重试逻辑。
-
\ No newline at end of file
diff --git a/static/images/design-document/workflow-architecture.jpg
b/static/images/design-document/workflow/workflow-architecture.jpg
similarity index 100%
rename from static/images/design-document/workflow-architecture.jpg
rename to static/images/design-document/workflow/workflow-architecture.jpg
diff --git a/static/images/design-document/workflow/workflow-demo-1.png
b/static/images/design-document/workflow/workflow-demo-1.png
new file mode 100644
index 000000000..8b380bd4a
Binary files /dev/null and
b/static/images/design-document/workflow/workflow-demo-1.png differ
diff --git a/static/images/design-document/workflow/workflow-demo-2.png
b/static/images/design-document/workflow/workflow-demo-2.png
new file mode 100644
index 000000000..636afda01
Binary files /dev/null and
b/static/images/design-document/workflow/workflow-demo-2.png differ
diff --git a/static/images/design-document/workflow/workflow-demo-3.png
b/static/images/design-document/workflow/workflow-demo-3.png
new file mode 100644
index 000000000..c17cf89dc
Binary files /dev/null and
b/static/images/design-document/workflow/workflow-demo-3.png differ
diff --git a/static/images/design-document/workflow/workflow-demo-4.png
b/static/images/design-document/workflow/workflow-demo-4.png
new file mode 100644
index 000000000..198156a7d
Binary files /dev/null and
b/static/images/design-document/workflow/workflow-demo-4.png differ
diff --git a/static/images/design-document/workflow-diagram.png
b/static/images/design-document/workflow/workflow-diagram.png
similarity index 100%
rename from static/images/design-document/workflow-diagram.png
rename to static/images/design-document/workflow/workflow-diagram.png
diff --git a/static/images/design-document/workflow-use-case.jpg
b/static/images/design-document/workflow/workflow-use-case.jpg
similarity index 100%
rename from static/images/design-document/workflow-use-case.jpg
rename to static/images/design-document/workflow/workflow-use-case.jpg
diff --git
a/versioned_docs/version-v1.10.0/design-document/01-event-handling-and-integration/06-workflow.md
b/versioned_docs/version-v1.10.0/design-document/01-event-handling-and-integration/06-workflow.md
index eff287bad..76dd8b773 100644
---
a/versioned_docs/version-v1.10.0/design-document/01-event-handling-and-integration/06-workflow.md
+++
b/versioned_docs/version-v1.10.0/design-document/01-event-handling-and-integration/06-workflow.md
@@ -6,7 +6,7 @@ Imaging you are building a simple Order Management System for
an E-Commerce Stor
For high availability and high performance, you architect the system using
event-driven architecture (EDA), and build microservice apps to handle store
frontend, order management, payment processing, and shipment management. You
deploy the whole system in a cloud environment. To handle high workloads, you
leverage a messaging system to buffer the loads, and scale up multiple
instances of microservices. The architecture could look similar to:
-
+
While each microservice is acting on its own event channels, EventMesh plays a
crucial role of doing Event Orchestration.
@@ -181,13 +181,13 @@ events:
The corresponding workflow diagram is the following:
-
+
## EventMesh Workflow Engine
In the following architecture diagram, the EventMesh Catalog, EventMesh
Workflow Engine and EventMesh Runtime are running in three different processors.
-
+
The steps running the workflow is the followings:
diff --git a/versioned_docs/version-v1.7.0/design-document/01-workflow.md
b/versioned_docs/version-v1.7.0/design-document/01-workflow.md
index d0e47495f..2e5e21db5 100644
--- a/versioned_docs/version-v1.7.0/design-document/01-workflow.md
+++ b/versioned_docs/version-v1.7.0/design-document/01-workflow.md
@@ -6,7 +6,7 @@ Imaging you are building a simple Order Management System for
an E-Commerce Stor
For high availability and high performance, you architect the system using
event-driven architecture (EDA), and build microservice apps to handle store
frontend, order management, payment processing, and shipment management. You
deploy the whole system in a cloud environment. To handle high workloads, you
leverage a messaging system to buffer the loads, and scale up multiple
instances of microservices. The architecture could look similar to:
-
+
While each microservice is acting on its own event channels, EventMesh plays a
crucial role of doing Event Orchestration.
@@ -181,13 +181,13 @@ events:
The corresponding workflow diagram is the following:
-
+
## EventMesh Workflow Engine
In the following architecture diagram, the EventMesh Catalog, EventMesh
Workflow Engine and EventMesh Runtime are running in three different processors.
-
+
The steps running the workflow is the followings:
diff --git
a/versioned_docs/version-v1.8.0/design-document/01-event-handling-and-integration/06-workflow.md
b/versioned_docs/version-v1.8.0/design-document/01-event-handling-and-integration/06-workflow.md
index eff287bad..76dd8b773 100644
---
a/versioned_docs/version-v1.8.0/design-document/01-event-handling-and-integration/06-workflow.md
+++
b/versioned_docs/version-v1.8.0/design-document/01-event-handling-and-integration/06-workflow.md
@@ -6,7 +6,7 @@ Imaging you are building a simple Order Management System for
an E-Commerce Stor
For high availability and high performance, you architect the system using
event-driven architecture (EDA), and build microservice apps to handle store
frontend, order management, payment processing, and shipment management. You
deploy the whole system in a cloud environment. To handle high workloads, you
leverage a messaging system to buffer the loads, and scale up multiple
instances of microservices. The architecture could look similar to:
-
+
While each microservice is acting on its own event channels, EventMesh plays a
crucial role of doing Event Orchestration.
@@ -181,13 +181,13 @@ events:
The corresponding workflow diagram is the following:
-
+
## EventMesh Workflow Engine
In the following architecture diagram, the EventMesh Catalog, EventMesh
Workflow Engine and EventMesh Runtime are running in three different processors.
-
+
The steps running the workflow is the followings:
diff --git
a/versioned_docs/version-v1.9.0/design-document/01-event-handling-and-integration/06-workflow.md
b/versioned_docs/version-v1.9.0/design-document/01-event-handling-and-integration/06-workflow.md
index eff287bad..76dd8b773 100644
---
a/versioned_docs/version-v1.9.0/design-document/01-event-handling-and-integration/06-workflow.md
+++
b/versioned_docs/version-v1.9.0/design-document/01-event-handling-and-integration/06-workflow.md
@@ -6,7 +6,7 @@ Imaging you are building a simple Order Management System for
an E-Commerce Stor
For high availability and high performance, you architect the system using
event-driven architecture (EDA), and build microservice apps to handle store
frontend, order management, payment processing, and shipment management. You
deploy the whole system in a cloud environment. To handle high workloads, you
leverage a messaging system to buffer the loads, and scale up multiple
instances of microservices. The architecture could look similar to:
-
+
While each microservice is acting on its own event channels, EventMesh plays a
crucial role of doing Event Orchestration.
@@ -181,13 +181,13 @@ events:
The corresponding workflow diagram is the following:
-
+
## EventMesh Workflow Engine
In the following architecture diagram, the EventMesh Catalog, EventMesh
Workflow Engine and EventMesh Runtime are running in three different processors.
-
+
The steps running the workflow is the followings:
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
