eventmesh icon indicating copy to clipboard operation
eventmesh copied to clipboard

Event Governance for choreography

Open vongosling opened this issue 4 years ago • 3 comments

Enhancement Request

Generally speaking, choreography is driven by events from the various services within a system. Each service consumes events, performs an action, and publishes events. There is no centralized coordination or logic and very useful for small/simple workflows. It also brings difficult to conceptualize if a lot of services are involved. and harder to debug & test if a lot of services are involved. IMO, this is an important focus for EventMesh, we could fill this gap in the industry by providing a standard, visualizable, and codeless serverless workflow implementation for eventing choreography.

Is your enhancement request related to a problem? Please describe

Event Governance

Describe the solution you'd like

Involve the community[1] and create a lightable serverless workflow implementation for serverless workflow.

[1] https://serverlessworkflow.io/

Describe alternatives you've considered

No

Additional context

No

vongosling avatar Oct 09 '21 00:10 vongosling

serverlessworkflow/specification#559

qqeasonchen avatar Oct 14 '21 09:10 qqeasonchen

the same with https://github.com/apache/incubator-eventmesh/issues/276

qqeasonchen avatar Dec 29 '21 09:12 qqeasonchen

we can discuss on this thread continue.

qqeasonchen avatar Mar 31 '22 12:03 qqeasonchen

Superseded by https://github.com/apache/eventmesh/issues/2179

Pil0tXia avatar Jan 19 '24 08:01 Pil0tXia