Cantara / distributed-saga

Implementation of the distributed-saga pattern consisting of separate java libraries for api, execution, and serialization
Apache License 2.0
0 stars 1 forks source link

ask about Saga #31

Open fizz12344321 opened 2 years ago

fizz12344321 commented 2 years ago

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 commented 2 years ago

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.