Intermediary Device Routing Database Requests

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In data communication networks, primary database servers expend resources generating and transmitting redirect responses for requests that can be processed by secondary servers, leading to inefficient resource utilization.

Innovation Solution

A device intermediates between clients and database servers, identifying request types and routing them to appropriate subsets of database servers based on load balancing, directing read requests to secondary servers and write requests to primary servers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the primary database server receives and processes all requests from clients, then all request types can be handled centrally, but the primary server consumes excessive resources generating redirect responses for read requests that could be handled by secondary servers

Engineering Contradiction:

Improvecentralized request handlingVSAvoidserver resource consumption

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent segments the database server system into primary servers (handling write requests) and secondary servers (handling read requests). The intermediary device further segments request routing by identifying request types and directing them to appropriate server subsets, thereby distributing the processing load and reducing resource consumption on any single server.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary device as a mediator between clients and database servers. This intermediary receives requests from clients, identifies the request type, and routes requests to appropriate subsets of database servers. This intermediary layer eliminates the need for primary servers to generate redirect responses, thereby reducing their resource consumption while maintaining reliable request handling.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Productivity

If the primary database server generates redirect responses for all read requests, then secondary servers can be utilized, but the primary server spends excessive resources on generating and transmitting these redirect responses

Engineering Contradiction:

Improvesecondary server utilizationVSAvoidenergy spent on redirect response generation

Core Design Contradiction:

ProductivityVSLoss of energy

Solution Approach 1:

The intermediary device performs preliminary action by identifying the request type before the request reaches the primary server. By pre-classifying requests as read or write operations and routing them to appropriate server subsets in advance, the system eliminates the need for primary servers to generate redirect responses, thereby reducing energy loss while maintaining secondary server utilization for read operations.

Inventive Principle:

Principle #10Preliminary action

3Device complexity

If all requests are routed through the primary database server, then request routing is simple, but network performance deteriorates due to the burden on primary servers

Engineering Contradiction:

Improverouting logic simplicityVSAvoidnetwork performance

Core Design Contradiction:

Device complexityVSSpeed

Solution Approach 1:

The intermediary device serves as a mediator that absorbs the complexity of request type identification and routing logic. This allows the primary servers to focus solely on processing write requests without the overhead of analyzing request types or generating redirect responses, thereby improving network performance and reducing latency while maintaining organized routing through the intermediary layer.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS10671622B2Systems and methods for redirect handling

Publication Date: 2020.06.02 CITRIX SYSTEMS INC

AI summary

The present invention is related to a method for routing requests among a plurality of database servers. A device intermediary to a client and a plurality of database servers receives a request to access a database provided by the plurality of database servers. The plurality of database servers can include a first database server configured to process write requests and one or more second database servers configured to process read requests. The device determines that the request to access the database is a read request. The device identifies, responsive to determining that the request is a read request, one of the one or more second database servers to send the request instead of the first database server. The device then transmits the request to the identified second database server.