[
https://issues.apache.org/jira/browse/SCB-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16889410#comment-16889410
]
José Cardoso commented on SCB-1386:
-----------------------------------
Imagine service A and service B that communicate asynchronously, with a saga
starting in service A. However, currently as soon as I send a message from A to
B the saga is automatically closed, but I and I want the saga to finish only
after service B is executed. Also, with the current situation , an eventual
compensation method in service B is never executed because the saga is already
closed. So I thought in this annotation to manually end the saga only in
service B.
> @SagaEnd annotation
> -------------------
>
> Key: SCB-1386
> URL: https://issues.apache.org/jira/browse/SCB-1386
> Project: Apache ServiceComb
> Issue Type: New Feature
> Components: Saga
> Affects Versions: pack-0.5.0
> Reporter: José Cardoso
> Priority: Major
>
> In an async environment (ex: microservices architecture communicating via
> messaging systems) it is important to control when the saga ends. Therefore,
> I propose a new annotation - @SagaEnd - to have the possibility to explicitly
> end the Saga, which will also allow the triggering of the compensation
> methods in case of failure.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
