Currently in the framework there is this persistent state machine mechanism called Saga.
From what i’ve read across books and articles i came up to conclusion that it is not exactly a saga.
My understanding is that saga needs to be component which explicit behavior is to compensate failures, so saga uses a process manager to handle some workflow but also is defining the compensating actions.
They both handle persistance so it all comes down is the intent of a component.
I’m not sure why this component was called that explicitly, any points on that would be helpful.
(I understand that it is quite cherry picking of naming things, but it would be insightful for me if i understand the axon’s decisions more clearly)