Client-Side Data Virtualization Driver for Direct Query Retrieval
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data virtualization servers incur significant performance overhead and processing delays due to the large volume of data retrieved in response to queries, leading to inefficiencies in query processing.
Innovation Solution
A versatile data virtualization driver is configured on the client side to bypass the virtualization server for direct data retrieval from data sources, using driver provision information and native queries to reduce server load and enhance efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If data virtualization servers are used to process queries and route data between client devices and backend data sources, then centralized data access management is achieved, but performance overhead and processing delays increase due to the significant volume of data being retrieved
Solution Approach 1:
The patent extracts the data retrieval function from the virtualization server and moves it to the client device. The client device provisions a driver that enables direct connection to backend data sources, bypassing the virtualization server for actual data transfer. This extraction eliminates the server as a bottleneck in the data path while maintaining its role in query routing and result aggregation.
Solution Approach 2:
The patent introduces a driver as an intermediary component that resides on the client device. This driver acts as a local mediator between the client application and backend data sources, enabling direct data access without requiring the virtualization server to handle the actual data transmission. The driver translates client requests into data source-specific protocols.
2Reliability
If data virtualization servers retrieve and route large volumes of data, then complete query results are delivered to clients, but server load and processing overhead increase significantly
Solution Approach 1:
The patent segments the data access architecture into three distinct components: the virtualization server for query management, the client-side driver for connection management, and backend data sources for data storage. This segmentation distributes the processing load across multiple components, with each handling specific tasks, thereby reducing the burden on the central server.
Solution Approach 2:
The client device provisions its own driver and establishes direct connections to data sources independently. This self-service approach allows the client to retrieve data directly without requiring the server to mediate every data transfer operation, significantly reducing server processing load while maintaining data retrieval completeness.
3Productivity
If direct data retrieval is implemented by bypassing the virtualization server, then processing efficiency improves, but system complexity increases due to client-side driver provisioning
Solution Approach 1:
The system performs preliminary provisioning of the driver on the client device before actual data retrieval operations. The virtualization server provides the necessary driver components and configuration information in advance, so that when data retrieval is needed, the client is already prepared with the appropriate driver, eliminating the need for complex runtime driver installation or configuration.
Solution Approach 2:
The driver is designed as a universal component that can interface with multiple types of backend data sources through a standardized protocol. This multi-functionality reduces client-side complexity by providing a single driver solution that can handle various data source types, eliminating the need for multiple specialized drivers or complex adaptation layers.
Data Source
AI summary
Methods and systems for data virtualization are described. A computing system may transmit, by a client device and to a data virtualization server, a data virtualization query directed to a data source. The computing platform may receive, by the client device and from the data virtualization server, driver provision information comprising data source connection information for the data source and a native version of the data virtualization query. The computing platform may provision, at the client device and using the driver provision information, a native data source driver corresponding to the data source. The client device may transmit, to the data source and using the provisioned native source driver, the native version of the data virtualization query. The client device may receive, from the data source, data source results, and may display the data source results.