You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 13, 2024. It is now read-only.
Q1: What problems the repeated SagaEndedEvent would cause?
Q2: It would write the same TxStartedEvent/TxEndedEvent in case of trying commit again.
Then what was the idea for initial design?
What problems the repeated TxStartedEvent/TxEndedEvent would cause?
Q3: Are there any other situations except above?
The text was updated successfully, but these errors were encountered:
Q1: As we have the EventScanner and the Saga starter caller to send the SagaEndedEvent.
But it's no harm if there are more than two SagaEndedEvent as the Saga processing is ended eventually.
Q2: The event should be logged incase of the service shutdown by accident.
Q3: Currently I don't think there any other bad situations which we need to deal with.
Q1: What problems the repeated SagaEndedEvent would cause?
Q2: It would write the same TxStartedEvent/TxEndedEvent in case of trying commit again.
Then what was the idea for initial design?
What problems the repeated TxStartedEvent/TxEndedEvent would cause?
Q3: Are there any other situations except above?
The text was updated successfully, but these errors were encountered: