US 12,014,191 B2
Using persistent finite state machine to coordinate lifecycle operations in service broker
Abhik Gupta, Bangalore (IN); Shivansh Rai, Sagar (IN); and Vineet Singh, Mumbai (IN)
Assigned to SAP SE, Walldorf (DE)
Filed by SAP SE, Walldorf (DE)
Filed on Aug. 30, 2021, as Appl. No. 17/460,890.
Prior Publication US 2023/0065589 A1, Mar. 2, 2023
Int. Cl. G06F 9/448 (2018.01); G06F 9/46 (2006.01); G06F 16/23 (2019.01); H04L 67/02 (2022.01); H04L 67/562 (2022.01)
CPC G06F 9/4498 (2018.02) [G06F 9/466 (2013.01); G06F 16/2379 (2019.01); H04L 67/02 (2013.01); H04L 67/562 (2022.05)] 20 Claims
OG exemplary drawing
 
1. A system associated with an Open Service Broker (“OSB”) Application Programming Interface (“API”) computing environment, comprising:
a persistent Finite State Machine (“FSM”), associated with an OSB API service broker, supports storage of in-memory representations of transitions and states in a persistent data structure;
an FSM library, including: an embedded document parser, logic to encapsulate serial and parallel executions of task functions, and methods or APIs to retrieve execution states;
a database storing a current state of the service broker; and
a state machine executor, including:
a computer processor, and
computer memory, coupled to the computer processor, storing instructions that, when executed by the computer processor cause the processor to:
retrieve the current state of the service broker from the database,
based on the current state, use the persistent FSM and FSM library to coordinate a distributed transaction workflow for the service broker, the distributed transaction workflow including asynchronous instance OSB API lifecycle operations that span multiple entities, and
update the database with state outputs for the service broker,
wherein a failure encountered during state or transition execution results in an automatic execution of compensable measures by the persistent FSM and the FSM library to recover from the failure.