Aggregate Nodes for Synchronous Timeout Handling in Middleware
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing middleware technology, specifically the WMB, fails to meet the timing requirements of frontend applications that need synchronous responses from backend applications, as the timeout settings in the WMB cannot be adjusted to match the required timeouts of these applications, leading to potential delays or timeouts in response delivery.
Innovation Solution
The implementation of aggregate nodes in the WMB, specifically the AggregateControl and AggregateReply nodes, allows for setting a predefined timeout that automatically pairs across nodes, ensuring that if a backend response is not received within this time, a timeout response is sent to the frontend application, thereby addressing the need for synchronous processing by managing message traffic effectively.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the WMB uses a fixed timeout node setting, then the system structure remains simple, but the timeout cannot meet the requirements of frontend applications needing synchronous responses
Solution Approach 1:
The patent applies dynamics by making the timeout value adjustable and configurable rather than fixed. The timeout node is enhanced to accept dynamic timeout values that can be set based on specific application requirements, allowing the system to adapt between synchronous and asynchronous operation modes as needed.
Solution Approach 2:
The patent changes the timeout parameter from a fixed system value to a configurable parameter. By allowing the timeout value to be modified through configuration files or programmatic settings, the system can adapt to different frontend application requirements without changing its fundamental architecture.
2Reliability
If the WMB sends asynchronous responses to backend applications, then the backend processing flexibility is improved, but the frontend applications cannot receive timely synchronous responses within required timeout periods
Solution Approach 1:
The patent segments the response handling into two distinct paths: synchronous response path for frontend applications and asynchronous processing path for backend applications. The timeout node monitors the synchronous path and can independently trigger timeout responses without interfering with backend processing efficiency.
Solution Approach 2:
The timeout node acts as an intermediary between the backend application and frontend application. It monitors the backend response and manages the timeout logic, sending timeout responses to frontend applications when needed while allowing the backend to continue processing asynchronously without restriction.
3Loss of time
If the timeout node is configured with a longer timeout, then fewer timeout errors occur, but the frontend applications with strict timing requirements experience delays
Solution Approach 1:
The patent enables dynamic adjustment of the timeout parameter to match specific application requirements. Frontend applications with strict timing requirements can be configured with shorter timeouts, while other applications can use longer timeouts, optimizing both response time and timeout error rates for different use cases.
Data Source
AI summary
A system includes a first node and a second node. The first node includes a first memory storing executable instructions for configuring the first node to receive a service request from a frontend application. The first node identifies a timeout required for processing the service request and sends the service request to a backend application for processing. The second node includes a second memory storing executable instructions for configuring the second node to monitor for a response regarding results of processing of the service request. In response to the timeout for the service request elapsing before receiving a backend application response to the service request, the second node sends a response informing the frontend application from which the service request was received that the backend application has not responded to the service request.