[
https://issues.apache.org/jira/browse/SCB-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16889506#comment-16889506
]
José Cardoso commented on SCB-1386:
-----------------------------------
I remembered of another possibility: we can use alpha server to coordinate
this. Alpha will have all the sub transactions/compensation methods registered
and will only trigger the end of saga event when all of the sub transactions
are done. In this scenario we don't need the annotation, the responsibility is
delivered to alpha.
> @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)
