[SCB-1258] Using StateMachine for tracing the transaction states

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Saga
• Labels: alpha
• Assignee: Lei Zhang
• Reporter: Willem Jiang
• Created: 17/Apr/19 08:22
• Updated: 23/Jun/23 19:21

Description

Using the state machine could reduce the code complexity of Alpha.
We could start a simple POC to verify the implementation.

We could also use it to trace the command sending states.

• Statemachine should handle timeout dynamically
• Statemachine should support message(event) persistent
• Support to the states of transaction from outside
• Statemachine cluster support

Issue Links

• Blocked: SCB-275 [pack] retry compensation on failure/timeout/crash
• Blocked: SCB-1438 Class ElasticsearchTransactionRepository synchronization save method is invalid
• mentioned in: Page Loading...

Sub-Tasks

• Prototyping the state machine design: Resolved
• Support for Akka-based Alpha clusters: Resolved
• Save the terminated transaction data to elasticsearch: Resolved
• Support for in-process nested global transactions: Open
• Support for query transaction data based on RESTful API: Open
• Collection state machine health to metrics: Resolved
• Improve acceptance testing for state machines: Open
• Implement Alpha Event Channel Plugin: Resolved
• We need to do something then transfer the states.: Resolved
• Add alpha benchmark tool document: Resolved
• Refactoring the core part of alpha-fsm module to move to alpha-core: Resolved
• Alpha Event Redis Channel Plugin: Resolved
• Alpha Event Kafka Channel Plugin: Resolved
• The retrieveDataMaps method throws a 500 error in acceptance-pack-akka-spring-demo: Closed
• State machine manual: Resolved
• Optimize class ElasticsearchTransactionRepository persistence parameters: Resolved
• Topic initialization & Class KafkaMessagePublisher needs to use globalTxId as the partitioning strategy.: Resolved