Orchestration of a sequence of computations by external systems

A method performed by one or more processors executing machine executable code, the method comprising:

• executing, by an orchestrator service, a workflow including a first controller and a second controller that succeeds the first controller, the first controller corresponding to a first microservice and including a first callout function and a first callback function, and the second controller corresponding to a second microservice and including a second callout function, wherein execution of the workflow includes execution of the first callout function that causes invocation of a first call to the first microservice;
• generating, by the orchestrator service, a first key identifier (ID) associated with the first callout function;
• receiving an event associated with a second key ID;
• associating the event with the first callout function if the first key ID matches the second key ID;
• receiving, by the orchestrator service, a notification of an execution state from the first microservice, the execution state being based on the invocation of the first call to the first microservice;
• transmitting, by the orchestrator service, the execution state to the first callback function;
• in response to transmitting the execution state to the first callback function, receiving a function output based on the execution state from the first callback function;
• determining, based on the function output, whether to execute the second callout function, wherein execution of the second callout function causes invocation of a second call to the second microservice;
• and
• in response to a determination to execute the second callout function, executing the second callout function.

A non-transitory machine-readable medium comprising executable code which when executed by one or more processors associated with a computing device are adapted to cause the one or more processors to perform a method comprising:

• executing a workflow including a first controller and a second controller that succeeds the first controller, the first controller corresponding to a first microservice and including a first callout function and a first callback function, and the second controller corresponding to a second microservice and including a second callout function, wherein execution of the workflow includes execution of the first callout function that causes invocation of a first call to the first microservice;
• generating, by the orchestrator service, a first key identifier (ID) associated with the first callout function;
• receiving an event associated with a second key ID;
• associating the event with the first callout function if the first key ID matches the second key ID;
• receiving a notification of an execution state from the first microservice, the execution state being based on the invocation of the first call to the first microservice;
• transmitting the execution state to the first callback function;
• in response to transmitting the execution state to the first callback function, receiving a function output based on the execution state from the first callback function;
• determining, based on the function output, whether to execute the second callout function, wherein execution of the second callout function causes invocation of a second call to the second microservice;
• and
• in response to a determination to execute the second callout function, executing the second callout function.