[Enhancement] Workflow Feature Implementation: Decouples workflow from application
Open
enhancement
help wanted
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 658
- Avg merge
- 11h 29m
- Merged PRs (30d)
- 52
Description
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/eventmesh/issues?q=is%3Aissue) and found no similar issues.
### Enhancement Request
Decouples workflow from application
### Describe the solution you'd like
Workflow subscribes to events, decouples workflow from application, and decides start or transition by workflow
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
Contributor guide
Research direction
The issue names no files, tests, or entry points. First map how EventMesh currently connects workflows to applications and how workflows subscribe to events; done means workflows can independently subscribe to events and decide when to start or transition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100