-
Notifications
You must be signed in to change notification settings - Fork 639
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Saga Transaction support #816
Comments
very useful function, let us do it. |
I am interested, can I join this? |
@qqeasonchen I'm quite interested about this problem and I'm a newbie in this community. Is there further discussion and actions? |
We can discuss here. |
Any followup here? I'm familiar with SEATA SAGA implementation, and have been contributing to it. If there is still a developing plan on this idea, I can study and share some thoughts. |
welcome to aboard |
1 similar comment
welcome to aboard |
@ptyin Welcome and you can join the Wechat group for instant messaging if it is more convenient for you. |
Search before asking
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?
The text was updated successfully, but these errors were encountered: