Load Balancing Utility for Transaction Request Processing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current computer programs that balance transaction requests with application processing either lead to delayed responses due to overloading or system overload when handling a large number of requests simultaneously.

Innovation Solution

A load balancing system comprising a message queue, trigger queue, load balancing utility, parameter file, applications, journal, and CICS recorder, which monitors and adjusts the number of applications processing transaction requests based on message queue load, ensuring efficient response handling without overloading the system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a large number of applications are started to process transaction requests simultaneously, then the system can handle more requests, but the system may be overloaded

Engineering Contradiction:
Improverequest processing capacityVSAvoidsystem stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system dynamically adjusts the number of applications based on real-time monitoring of transaction request queues. The load balancing utility continuously monitors queue lengths and starts or stops applications accordingly, allowing the system to adapt its processing capacity to match actual demand rather than maintaining a fixed number of applications

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system implements feedback mechanisms where the load balancing utility monitors the state of transaction request queues and uses this information to control application startup and termination. This closed-loop control ensures that applications are started only when needed and stopped when queues are clear, preventing system overload while maintaining adequate processing capacity

Inventive Principle:
Principle #23Feedback

2Productivity

If applications are started to process transaction requests, then requests can be handled, but response delays may occur when many requests arrive simultaneously

Engineering Contradiction:
Improverequest processing speedVSAvoidresponse delay
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system pre-positions applications in a ready state before transaction requests arrive. By monitoring queue lengths in advance and starting applications proactively when queues build up, the system avoids the delay of having to start applications after requests have already accumulated, thereby reducing response time

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system maintains continuous monitoring and processing activity by keeping applications running when queues have sufficient transactions. This continuous operation eliminates idle periods and ensures that transaction requests are processed without interruption, maintaining steady processing speed and minimizing response delays

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS8973001B2Processing transaction requests using a load balancing utility and multiple operating parameters
Publication Date: 2015.03.03 BANK OF AMERICA CORP
  • US8973001B2 patent drawing
  • US8973001B2 patent drawing
  • US8973001B2 patent drawing

AI summary

Methods, computer readable media, and apparatuses for balancing the number of transaction requests with the number of applications running and processing information for those transaction requests are presented. According to one or more aspects, a message queue receives one or more messages, each including a transaction request, from a computing device. The message queue sends a trigger message to a trigger queue. The load balancing utility monitors the number of messages in the message queue and determines a number of transaction requests to process and starts a number of additional applications to process the additional transaction requests. The applications process the transaction requests and send a response for each of the transaction requests to the message queue. The message queue sends the response back to the computing device.