You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eventmesh.apache.org by mikexue <mi...@apache.org> on 2022/11/02 09:53:26 UTC
EventMesh WorkFlow Engine design meeting
Conference theme: EventMesh WorkFlow design discussion
Conference Time: 2022/10/31 20:15-21:30 (GMT+08:00) China Standard
Time - Beijing
Click the link to join the meeting, or add to the meeting list:
https://meeting.tencent.com/dm/vMePKTshOeEX
#TencentMeeting: 374-923-135
Host: walter
Attendee: Eason Chen, mikexue, horoc
Meeting Detail:
1.Shows how to run the EventMesh WorkFlow
2.Explain the process of EventMesh WorkFlow demo
3.Discuss subsequent workflow feature development plans:
Total target:task scheduler, queue, store can be deployed alone,
horizontal extension
- The workflow engine subscribes to the event to decouple the workflow
engine from the application, and the workflow engine decides to start
or transition)
- Decoupled task from scheduler and extended scheduler plugin to
integrate the distributed scheduling engine
- Observability :tracing/metric, integrated OpenTelemetry
- event-filter/event-validate: based on SW Spec implementation
- workflow queue integrates Message Queue
- workflow-event storage, storage and computation separation
- Integrated with eventmesh-dashboard
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org