Gateway Query Identification for Multi-Tier Database Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In a multi-tier environment, existing technologies are limited in manipulating data within a remote database across multiple servers due to non-unique data handles or locators, leading to incorrect data retrieval and potential data integrity issues.
Innovation Solution
A system and method that utilize a gateway system to generate and map a unique query identification, ensuring that queries are forwarded to the correct target server for processing, using a query manager module to associate the gateway query identification with the intended target server, thereby ensuring correct data manipulation without data retrieval.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If data objects are transmitted across the network for manipulation, then data manipulation can be performed, but network bandwidth is consumed and network traffic increases
Solution Approach 1:
The patent extracts only the essential identifier (handle/locator) from the data object and transmits it across the network instead of the entire data object. This allows the client to manipulate data remotely by sending minimal identification information rather than large data payloads, significantly reducing network bandwidth consumption while maintaining data manipulation functionality.
Solution Approach 2:
The patent creates and transmits a lightweight copy (handle/locator) that references the original data object stored on the server. This handle contains sufficient information to identify and manipulate the data without requiring the actual data to be copied or transmitted, enabling efficient remote data operations with minimal network traffic.
2Loss of energy
If handles are used to identify data objects remotely, then network bandwidth is conserved, but the system is limited to two-tier configurations and cannot work across multiple database servers
Solution Approach 1:
The patent introduces a gateway server as an intermediary layer between the client and multiple backend database servers. The gateway server manages handle translation and routing, allowing handles to be unique and meaningful across the entire multi-tier system rather than being limited to individual servers. This intermediary enables clients to manipulate data across multiple database servers using the same handle-based approach that conserves network bandwidth.
Solution Approach 2:
The patent creates a universal handle system that works across multiple database servers through the gateway. The gateway translates server-specific handles into gateway-wide unique identifiers, making the handle mechanism universally applicable across the entire distributed system rather than being confined to single-server two-tier architectures.
3Reliability
If data is retrieved from the remote database for manipulation, then complete data access is achieved, but storage capacity is consumed and network traffic increases
Solution Approach 1:
The patent extracts only the handle (a minimal identifier) from the data object and keeps the full data object stored on the remote server. This allows the client to perform operations on the data using only the small handle, avoiding the need to store or retrieve large data objects locally, thus conserving storage capacity while maintaining complete data access capability.
Data Source
AI summary
An embodiment of the present invention enables manipulation of data on a remote server and ensures uniqueness of data identifiers in a multi-tier environment, where a database client communicates through one or more intermediate servers to reach the target server containing the remote database. In particular, a client system transmits a query to the target server via a gateway system and receives a handle or data reference and a query identification for subsequent manipulation of data residing on that target server. A new query identification is generated by the gateway system and mapped with the query identification of the intended target server. When the client system transmits a query with the gateway query identification, the gateway system performs a lookup operation to identify the corresponding target server and subsequently forwards the query and target server query identification to the identified target server for processing.