Abstract: Event-driven architecture for control microservices. In some implementations, the system generates a graphical user interface including one or more screen elements for receiving input values for a resource request. Based on determining that the user has navigated away from a current screen element, the system executes, by a control microservice, control logic associated with the current screen element and compares 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, the system executes a detective control that asynchronously routes the resource request to an exception-handling queue. Based on the control logic raising an exception and execution time being within the latency threshold, the system executes a preventive control that blocks or corrects the one or more input values before the resource request is executed.

Abstract: Event-driven architecture for resource execution. In some aspects, the system receives a resource request and selects a workflow template to handle the request. Using the selected template, the system creates a first workflow instance that includes a first set of microservices. After executing some microservices, the system receives a modified resource request. The system pauses the first workflow instance, and based on the modified request, selects a different workflow template to handle the modified request. Using this template, the system creates a second workflow instance that includes a second set of microservices. However, before executing the modified request, the system identifies microservices that are common between the first and second sets. For these overlapping microservices, the system determines which outputs from the first set can be reused for the second set. The system initiates the second workflow instance to continue executing the modified request.