Details
-
Type:
New Feature
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: 5.x Backlog
-
Component/s: Transaction
-
Labels:
-
Last commented by a User:true
Description
In the world of MicroServices, Saga transactions are a way to ensure that you can enroll multiple service calls into a workflow so that you can execute a long-running transaction without having to take any locks or imply a 2PC transaction manager, which is not suitable in a distributed system scenario where processing times can be invariable.
Currently, there is little support for the Saga pattern. I also found that Axon supports it, and possibly Narayana.
It would be great if we can discuss if there is a way to add this in Spring framework since it's definitely a handy feature. I assume that Sagas go hand-in-hand with the Spring 5 Reactive approach.
