Event Handler Orchestrator for Synchronous Cross-Domain Logic Injection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In computing systems, event handlers in separate domains face challenges in processing results from asynchronous event handlers before the completion of the operation that raised the event, limiting their ability to inject logic synchronously.
Innovation Solution
An event handler orchestrator service stores records for event handlers across different domains, filters interested handlers, and provides endpoints for invoking processes to call them synchronously, allowing in-line logic execution without altering the invoking process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If event handlers in separate domains are called asynchronously, then domain independence is maintained, but the ability to process results before operation completion is lost
Solution Approach 1:
The patent introduces an event handler registration mechanism that acts as an intermediary between domains. Event handlers in separate domains register their interests with the originating domain, allowing synchronous invocation while maintaining domain independence. The registration table stores handler information that can be retrieved and invoked synchronously without direct cross-domain coupling.
Solution Approach 2:
Event handlers are registered in advance before events occur. This preliminary registration allows the system to have ready-made handlers that can be synchronously invoked when events are raised, eliminating the need for asynchronous processing and result waiting.
2Device complexity
If event handlers are invoked asynchronously from separate domains, then system modularity is preserved, but logic injection capability is reduced
Solution Approach 1:
The registration mechanism serves as an intermediary that enables logic injection. By registering handlers with the originating domain through this intermediary, handlers can be synchronously invoked to inject logic into the operation flow, while the intermediary maintains system modularity by handling the cross-domain communication details.
Solution Approach 2:
The event handler registration table serves multiple functions: it stores handler information for synchronous invocation, maintains domain independence, and enables logic injection. This multi-functional mechanism resolves the contradiction by providing a universal solution that supports both modularity and logic injection.
3Speed
If in-line event handlers are used within the same domain, then synchronous processing is achieved, but domain coupling increases
Solution Approach 1:
The registration mechanism acts as an intermediary that enables synchronous processing without direct domain coupling. Event handlers in separate domains register with the originating domain, allowing synchronous invocation while the intermediary manages the coupling abstraction, preventing direct domain dependencies.
Solution Approach 2:
The system segments event handling into registration (performed once) and invocation (performed synchronously). This segmentation allows handlers to be defined in separate domains while being invoked synchronously in the originating domain, reducing coupling while maintaining processing speed.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Event handler records, for different event handlers in different domains, are stored in an event handler orchestrator service. The event handler records identify event handlers (in various domains) that are to handle events raised in separate domains. When an event is raised, the event handler records are filtered to identify an event handler that has indicated an interest in the raised event, and an end point corresponding to the identified event handler is provided back to the calling process. The calling process then invokes the event handler for which the end point is returned.