Middleware Service Request Sequencing and Load Balancing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Servers face operational overload and poor service processing efficiency due to large service requests, and the sequence of service request results returned to clients is often inconsistent with the sequence of requests sent, especially affected by network load and server hardware factors.
Innovation Solution
A middleware system that includes a processor and storage apparatus with service agent, time agent, and message distributor units, which receives and sequences service requests, outputs them to multiple servers, records request times, and builds a message distribution table to ensure service request results are returned in the same order they were received.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a server receives a large number of service requests, then service processing capacity is improved, but operational load increases and service processing efficiency deteriorates
Solution Approach 1:
The system segments service requests into different queues based on their arrival sequence, with each queue managed independently. The first queue stores requests received earlier while the second queue stores requests received later, allowing parallel processing without mutual interference, thus maintaining both high capacity and efficiency
Solution Approach 2:
A message distributor acts as an intermediary between the queues and the service request end. It coordinates the retrieval of requests from different queues and the return of results, ensuring that the service processing system can handle large volumes of requests while maintaining efficiency through centralized control
2Productivity
If service requests are processed by multiple servers, then processing capacity is improved, but the sequence consistency of service request results deteriorates
Solution Approach 1:
The system performs preliminary actions by recording the arrival sequence of service requests before they are processed. Time markers are attached to each request based on their arrival time, and this sequence information is preserved throughout the processing pipeline, ensuring that results can be returned in the correct sequence regardless of which server processes which request
Solution Approach 2:
The message distributor uses feedback from the time markers associated with each service request to determine the correct sequence for returning results. By continuously monitoring the sequence information and coordinating the return of results based on this feedback, the system maintains sequence consistency even when multiple servers process requests in parallel
Data Source
AI summary
A middleware system and a service request result returning method are provided. The middleware system communicates with a service request end and a plurality of servers. A processor receives a plurality of service requests sent by the service request end, and writes the service requests into a service request queue. The service agent unit outputs the service requests to the servers according to the service request queue. The servers respond with a plurality of service request results to the service agent unit. The time agent unit detects the time when the processor receives the service requests, so as to write a plurality of service request end messages and a plurality of service request times of the service requests into a service request time queue. The message distributor builds a message distribution table, and outputs the service request results to the service request end according to the message distribution table.