[Feature] Saga Transaction support
- 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.
### Feature Request
More and more customers want to implement consistent distributed transactions based on the event-driven architecture. Currently, there are some practices around saga in the industry. However, the cost is high and the availability is poor. So, I'm here to propose a new transaction model, and you're welcome to take the task.
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
Contributor guide
Research direction
The issue proposes Saga transaction support for EventMesh's event-driven middleware but names no files, tests, APIs, or implementation boundary. Start by reviewing the existing transaction and event-processing architecture, then determine the required Saga model and scope. Done requires an agreed design and complete support validated by appropriate tests, which are not identified here.
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
- 20/100