Event-driven control microservices architecture

A method for an event-driven control microservices architecture, the method comprising:

• receiving, from a client device, an indication from a user to initiate data entry for a resource request;
• in response to the indication, generating a graphical user interface displayable on the client device,
• wherein the graphical user interface includes one or more screen elements for receiving input values for the resource request, and
• wherein each screen element is associated with control logic embedded in a control microservice;
• determining that the user has navigated away from a current screen element;
• in response to determining that the user has navigated away from the current screen element, invoking the control microservice with an event payload including an indication of the current screen element and one or more input values from the current screen element;
• executing, by the control microservice, control logic associated with the current screen element and comparing an execution time for the control logic against a latency threshold;
• based on the control logic raising an exception and execution time being within the latency threshold, executing a preventive control that blocks and/or corrects the one or more input values before the resource request is executed;
• based on the one or more input values for the resource request, selecting, from a plurality of workflow templates, a workflow template suitable for executing the resource request;
• providing, based on the workflow template, a workflow instance including a plurality of microservices for executing the resource request;
• and
• performing the workflow instance for executing the resource request.

A system comprising at least one processor and one or more non-transitory computer-readable media having instructions stored thereon that, when executed by the at least one processor, cause the at least one processor to perform operations comprising:

• receiving, from a client device, an indication to initiate data entry for a resource request;
• in response to the indication, generating an interface,
• wherein the interface includes one or more elements for receiving input values for the resource request, and
• wherein each element is associated with control logic embedded in a control microservice;
• determining that one or more values have been received for a current element;
• in response to determining that the one or more values have been received for the current element, invoking the control microservice with an event payload including an indication of the current element and one or more input values from the current element;
• executing, by the control microservice, control logic associated with the current element and comparing an execution time for the control logic against a latency threshold;
• based on the control logic raising an exception and the execution time exceeding the latency threshold, executing a detective control that asynchronously routes the resource request to an exception-handling queue;
• and
• based on the control logic raising an exception and execution time being within the latency threshold, executing a preventive control that blocks or corrects the one or more input values before the resource request is executed.