Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
saga-0.1.0
-
None
Description
Currently, SagaEndedEvent is sent immediately after receiving responses of sub transactions. However, this behavior is incorrect when handling asynchronous compensation as compensation may have some delay. To simplify this, we suppose the error response code will throw an exception to the SagaStart node. In this way, the normal responses will send out the SagaEndedEvent immediately when they finish while the failed transaction will complement the SagaEndedEvent when the compensations complete.
Attachments
Issue Links
- links to