-
Notifications
You must be signed in to change notification settings - Fork 45
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
Saga and undo logic #257
Labels
Comments
I have considered using ETCD as an event-driven engine to implement saga pattern, but DBPack is focused on database proxy, we can cooperate in hptx to implement saga pattern. What do you think? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there are support for sagas with compensation logic ?
I used to work on these types of 2PC systems and the holding of locks on DB’s is imho only allowed on Databases your own . Even with a large organisation with many teams where each team controls their own database, holding locks on more than db can be disallowed.
the alternative can be sagas where the transactions do not use locks , and is any db refuses a mutation, then the 2PC must execute compensation logic and either undo the transaction or some other form of compensation.
Are you working on this. I lock approach or interested in pursuing it ?
It’s a solution to when different parties need to perform business transactions across theirs and others databases.
if you would like to discuss more in depth on this I am open to collaborating. Telegram is in my GitHub profile.
The text was updated successfully, but these errors were encountered: