Asynchronous handling of service requests

A system comprising:

• one or more hardware processors;
• and
• one or more one or more non-transitory computer-readable media storing instructions, which when executed by the one or more hardware processors, cause execution of operations comprising:
• receiving, from a requesting entity to a web service, a request comprising a function identifier and function input, wherein the function identifier identifies a package of functions and a particular function in the package of functions;
• responsive to receiving the message:
• selecting a first event handler, of a plurality of event handlers, to process the request,
• wherein selecting the first event handler comprises instantiating the first event handler, and
• wherein selecting the first event handler is based on at least one system optimization criterion comprising a load balancing criterion;
• converting, before instantiating the first event handler, the message to a normalized message format associated with the first event handler;
• translating, via the first event handler, the function identifier to a native function call;
• initiating execution of the native function call using the function input;
• receiving output corresponding to the execution of the native function call;
• terminating the first event handler prior to receiving the output corresponding to the execution of the native function call, wherein the first event handler does not handle the output corresponding to the native function call;
• responsive to receiving the output corresponding to the execution of the native function call:
• selecting a second event handler, of the plurality of event handlers, to process the output,
• wherein selection of second event handler to process the output is independent of selection of the first event handler to process the request,
• wherein selection of the event handler to process the output is independent of which event handler was selected to process the request, and
• wherein selecting the second event handler comprises instantiating the second event handler;
• converting, before instantiating the second event handler, the return value to the normalized message format;
• generating, at least in part by the second event handler, a response based on the output;
• converting, before transmitting the response to the requesting entity, the response to a message format supported by the requesting entity;
• and
• transmitting the response to the requesting entity,
• wherein the message further comprises a callback uniform resource locator (URL), and wherein transmitting the response comprises accessing the callback URL, and
• wherein the response indicates a location where the output corresponding to the execution of the native function call is stored, the location being accessible to the requesting entity.

A method comprising:

• receiving, from a requesting entity to a service, a request comprising a function identifier and function input;
• responsive to receiving the message:
• selecting a first event handler, of a plurality of event handlers, to process the request;
• translating, via the first event handler, the function identifier to a native function call;
• initiating execution of the native function call using the function input;
• receiving output corresponding to the execution of the native function call;
• responsive to receiving the output corresponding to the execution of the native function call:
• selecting a second event handler, of the plurality of event handlers, to process the output;
• generating, at least in part by the second event handler, a response based on the output;
• and
• transmitting the response to the requesting entity.
• wherein the method is performed by at least one device comprising a hardware processor.