Event to serverless function workflow instance mapping mechanism

Abstract

A network mapping events to workflow instances. One or more event messages are received with an embedded token from one or more event sources associated with an application. A workflow specification is received that specifies a location of the token embedded in the one or more event messages, and the token is extracted from the one or more event messages using the location of the token specified in the workflow specification. The events are then mapped to a workflow instance of the application based on the token the one or more event messages.

What is claimed is: 
     
       1. A method of mapping events to workflow instances by a controller in a network, comprising:
 receiving an event message with an embedded token from an event source associated with one of a plurality of applications, the event message corresponding to occurrence of an event triggered at the event source; 
 receiving, from a serverless system, a workflow specification which defines a workflow template for a workflow of events and that specifies a location of the token embedded in the event message, the event token being different for each of the plurality of applications; 
 parsing the workflow specification to identify the location of the token embedded in the event message and storing the location of the token embedded in the event message into storage; 
 extracting, by a processor, the token embedded in the event message using the location of the token identified in the storage; and 
 mapping, by the processor, the event to a workflow instance of the one of the plurality of applications based on the token extracted from the event message to maintain a state of the workflow of events for the one of the plurality of applications which is mapped to the workflow instance. 
 
     
     
       2. The method of  claim 1 , wherein the mapping further comprises:
 creating the workflow instance; 
 adding an entry in a table of memory including a mapping of the token extracted from the event message to the workflow instance; and 
 sending the event associated with the token to the workflow instance associated with the token for processing. 
 
     
     
       3. The method of  claim 1 , wherein the mapping further comprises:
 retrieving an entry from a table in memory, the entry including a mapping of the token extracted from the event message to the workflow instance; and 
 sending the event to the workflow instance identified in the entry using the token. 
 
     
     
       4. The method of  claim 1 , wherein the workflow specification is instantiated as the workflow instance when events including the token embedded in the event message are received from the event source of the one of the plurality of applications. 
     
     
       5. The method of  claim 1 , wherein the workflow specification defines an internal state machine and the event that triggers a state in the internal state machine. 
     
     
       6. The method of  claim 1 , wherein the token is used to associate a group of events within the same workflow instance. 
     
     
       7. A controller for mapping events to workflow instances in a network, comprising:
 a non-transitory memory storage comprising instructions; and 
 one or more processors in communication with the memory, wherein the one or more processors execute the instructions to:
 receive an event message with an embedded token from an event source associated with one of a plurality of applications, the event message corresponding to occurrence of an event triggered at the event source; 
 receive a workflow specification which defines a workflow template for a workflow of events and specifying a location of the token embedded in the event message, from a serverless system, the token being different for each of the plurality of applications; 
 parse the workflow specification and storing the location of the token embedded in the event message into storage; 
 extract, by a processor, the token embedded in the event message using the location of the token identified in the storage; and 
 map the event to a workflow instance of one of the plurality of applications based on the token extracted from the event message to maintain a state of the workflow of events from the one of the plurality of applications which is mapped to the workflow instance. 
 
 
     
     
       8. The controller of  claim 7 , wherein the one or more processors further execute the instructions to:
 create the workflow instance; 
 add an entry in a table of memory including a mapping of the token extracted from the event message to the workflow instance; and 
 send the event associated with the token to the workflow instance associated with the token for processing. 
 
     
     
       9. The controller of  claim 7 , wherein the one or more processors further execute the instructions to:
 retrieve an entry from a table in memory, the entry including a mapping of the token extracted from the event message to the workflow instance; and 
 send the event to the workflow instance identified in the entry using the token. 
 
     
     
       10. The controller of  claim 7 , wherein the workflow specification is instantiated as the workflow instance when events including the token embedded in the event message are received from the event source of the one of the plurality of applications. 
     
     
       11. The controller of  claim 7 , wherein the workflow specification defines an internal state machine and the event that triggers a state in the internal state machine. 
     
     
       12. The controller of  claim 7 , wherein the token is used to associate a group of events within the same workflow instance. 
     
     
       13. A non-transitory computer-readable medium storing computer instructions for mapping events to workflow instances by a controller in a network, that when executed by one or more processors, cause the one or more processors to perform the steps of:
 receiving an event message with an embedded token from an event source associated with one of a plurality of applications, the event message corresponding to occurrence of an event triggered at the event source; 
 receiving, from a serverless system, a workflow specification which defines a workflow template for a workflow of events and that specifies a location of the token embedded in the event message, the event token being different for each of the plurality of applications; 
 parsing the workflow specification and storing the location of the token embedded in the event message into storage; 
 extracting, by a processor, the token embedded in the event message using the location of the token identified in the storage; and 
 mapping, by the processor, the event to a workflow instance of the application based on the token extracted from the event message to maintain a state of the workflow of events for the one of the plurality of applications which is mapped to the workflow instance. 
 
     
     
       14. The non-transitory computer-readable medium of  claim 13 , wherein the one or more processors further to perform the steps of:
 creating the workflow instance; 
 adding an entry in a table of memory including a mapping of the token extracted from the event message to the workflow instance; and 
 sending the event associated with the token to the workflow instance associated with the token for processing. 
 
     
     
       15. The non-transitory computer-readable medium of  claim 13 , wherein the one or more processors further to perform the steps of:
 retrieving an entry from a table in memory, the entry including a mapping of the token extracted from the event message to the workflow instance; and 
 sending the event to the workflow instance identified in the entry using the token. 
 
     
     
       16. The non-transitory computer-readable medium of  claim 13 , wherein the workflow specification is instantiated as the workflow instance when events including the token embedded in the event message are received from the event source of the one of the plurality of applications.