[Enhancement] 能否将EventMesh进化成为统一流程引擎
- 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
企业应用中有审批流、工作流、还有类似EventMesh的事件流。。
### Describe the solution you'd like
想咨询一下，现在计划重新架构公司级统一平台，能否基于EventMesh进行扩展，加入支持类似flowable的审批流，统一支撑所有的流程（审批流、工作流、事件流等）。而不是事件流一套架构、审批流又一套架构。。
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [ ] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) *
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by reviewing EventMesh's current architecture and the requested relationship to Flowable, then clarify the scope and acceptance criteria for a unified approval, workflow, and event-flow engine before implementation can be considered done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100