Skip to content
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

ask about Saga #31

Open
fizz12344321 opened this issue Jul 1, 2022 · 1 comment
Open

ask about Saga #31

fizz12344321 opened this issue Jul 1, 2022 · 1 comment

Comments

@fizz12344321
Copy link

Hi, i am reading your project and I love it. But i have a question, what queue do you use for the message queue, how do you manage the state of each service and how do you tackle and implement "Transaction outbox ". Thank u so much

@kimcs
Copy link
Member

kimcs commented Jul 4, 2022

The message-queue will be a bounded in-memory work queue in front of the thread-pool needed by the saga-execution-coordinator. The saga-log acts as persistent state cluster-wide and will handle forward (or backward) recovery so that we get eventual consistency of all saga executions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants