Adaptive Load Balancing in Transactional Middleware
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Transactional middleware systems face challenges in achieving accurate load balancing across multiple machines, as existing methods rely on static load calculations, which do not reflect real-time workload dynamics, leading to inefficiencies in service response times and resource utilization.
Innovation Solution
A system and method that maintain adaptive service response time tables on each transactional middleware machine, synchronized by associated synchronization servers, allowing clients to make dynamic routing decisions based on current service response times, and utilizing a dynamic request broker for precise load balancing across multiple machines.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If static load calculations are used for load balancing, then the system structure is simple, but the load balancing accuracy deteriorates
Solution Approach 1:
The patent transforms the static load balancing approach into a dynamic one by continuously measuring service response times and updating routing decisions in real-time. The system dynamically adjusts load distribution based on current system state rather than relying on predetermined static calculations, thereby improving load balancing accuracy while accepting increased system complexity.
Solution Approach 2:
The patent implements a feedback mechanism where service response times are continuously measured and fed back to the routing system. This feedback loop enables the system to adaptively adjust load balancing decisions based on actual performance data, improving accuracy by using real-time measurements rather than static calculations.
2Measurement precision
If dynamic service response time measurement is implemented, then load balancing accuracy is improved, but the device complexity increases
Solution Approach 1:
The patent implements self-service by having the transactional middleware system automatically measure its own service response times and use this information for routing decisions. The system monitors itself without requiring external measurement tools, thereby improving load balancing accuracy while minimizing the additional complexity introduced by self-monitoring mechanisms.
Solution Approach 2:
The patent makes the transactional middleware system multi-functional by combining transaction processing, performance measurement, and load balancing routing in a single integrated system. This universality reduces overall system complexity by eliminating the need for separate dedicated measurement and routing systems.
3Reliability
If service response time tables are synchronized across multiple machines, then load balancing reliability is improved, but the communication overhead increases
Solution Approach 1:
The patent implements periodic synchronization of service response time tables across transactional middleware machines rather than continuous real-time synchronization. This periodic approach maintains load balancing reliability by ensuring all machines have up-to-date information while reducing communication overhead by synchronizing at intervals rather than continuously.
Data Source
AI summary
A system and method can support accurate load balancing in a transactional middleware machine environment with a plurality of transactional middleware machines. A service response time table can be maintained on each transactional middleware machine in the transactional middleware machine environment, wherein said service response time table is adaptive to be used by a client on the transactional middleware machine to make routing decisions for a service request. The transactional middleware machine environment can further include a plurality of synchronization servers, with each said synchronization server associated with a transactional middleware machine in the transactional middleware machine environment. The plurality of synchronization servers operates to periodically synchronize the service response time table on each said transactional middleware machine in the transactional middleware machine environment.