Using the state machine could keep the Alpha transaction states tracing code simple . We could also use it to trace the command sending states.
Here are some feature requirement of the StateMachine:
- Statemachine should handle timeout dynamically
- Statemachine should support message(event) persistent
- Support to the states of transaction from outside
- Statemachine should have cluster support
Saga States:
SagaTransaction
→ LocalTransaction ...
→ SagaTransaction
→ LocalTransaction ...
Actor could send message to its parent to notify the state change of transactions, we just need to trace the "SagaStarted", "SagaSuspended", "SagaAborted", "SagaAborted", "SagaEnded", "TxStarted","TxFailed","TxEnded".
JIRA: SCB-1258 - Getting issue details... STATUS