Web-Based Database Interface System Load Balancing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional stream-based connections for database management systems, such as those using TCP/IP, face challenges in load balancing, resilience to connection interruptions, and firewall compatibility, limiting flexibility and reliability in routing database requests across servers.

Innovation Solution

A web-based database interface system utilizing HTTP or HTTPS protocols, which allows for request/response-based communication, enabling easier load balancing, resilience to connection interruptions, and compatibility with firewalls by using a load balancer and request coordinator store to manage and route database requests across multiple workers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If stream-based TCP/IP connections are used for database communication, then connection persistency is maintained, but flexibility to route connections to different servers for load balancing is lost

Engineering Contradiction:
Improveconnection persistencyVSAvoidrouting flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system segments the database access functionality into multiple independent worker servers that can be individually routed. The load balancer divides incoming connections and distributes them to different workers, allowing flexible routing while maintaining reliable connections through each worker's persistent connection to the database server.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The load balancer acts as an intermediary between clients and database workers, receiving client requests and routing them to appropriate workers. This intermediary enables flexible load distribution across multiple workers while each worker maintains its own persistent connection to the database server, resolving the contradiction between routing flexibility and connection reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If DBMS internal fail-over algorithms are used, then some resilience is provided, but effective resource distribution across all connections is not achieved

Engineering Contradiction:
Improveresilience to connection failureVSAvoidresource distribution efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system implements dynamic load balancing where the load balancer continuously monitors worker status and dynamically adjusts connection routing based on current resource utilization. This dynamic approach enables both effective resource distribution across workers and automatic fail-over when workers become unavailable, improving both productivity and reliability compared to static DBMS internal algorithms.

Inventive Principle:
Principle #15Dynamics

3Ease of operation

If TCP/IP ports are used for database communication, then direct server-to-server communication is enabled, but firewall compatibility is poor

Engineering Contradiction:
Improvedirect communication capabilityVSAvoidfirewall blocking
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The load balancer serves as an intermediary that receives connections on standard web ports (80/443) from clients and forwards them to database workers. This intermediary approach enables firewall compatibility by using commonly allowed web ports while maintaining direct communication capabilities between workers and the database server through separate internal connections.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system makes the database access interface universal by supporting both direct worker-to-database communication and load-balanced routing through the load balancer. This multi-functionality allows the same infrastructure to operate with or without firewalls, adapting to different network environments while maintaining ease of operation.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS12028336B2Highly available web-based database interface system
Publication Date: 2024.07.02 XACTLY CORP
  • US12028336B2 patent drawing
  • US12028336B2 patent drawing
  • US12028336B2 patent drawing

AI summary

Techniques are provided for a highly available web-based database interface system (WDIS) processing database requests that target one or more databases managed by a coupled DBMS. In an embodiment, a web server of multiple web servers receives a first client web-based request that includes one or more first database instructions of a database request. The multiple web servers are configured to balance client web-based requests among one or more of the multiple web servers. The one or more of the multiple web servers are coupled to a database management system that includes one or more database servers executing database instructions on one or more databases. Based on balancing client web-based requests among the one or more of the multiple web servers, routing the first client web-based request that includes the one or more first database instructions of the database request to the first web server of the one or more multiple web servers coupled to the database management system. A request coordinator store coupled to the one or more of the multiple web server is queried. to determine a state of the database request. Based at least in part on the state of the database request, the first web server requests the database management system to execute the one or more first database instructions and update the state.