Asynchronous Interface for Distributed Data Retrieval
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Complex queries across multiple databases in retail environments are inefficient due to the need for separate queries and significant time to execute, especially when customer data is stored in separate databases for privacy and security reasons.
Innovation Solution
An integrated asynchronous interface with APIs for data retrieval, decomposing search requests into sub-search requests distributed across multiple data sources, aggregating responsive data, and using APIs to maintain status and provide responses, simplifying data retrieval across unaffiliated databases.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If separate queries are issued to separate databases to retrieve customer data, then data retrieval from distributed data sources is achieved, but query complexity and execution time increase significantly
Solution Approach 1:
The system segments a complex query into multiple sub-queries that are distributed to different data sources. The query interface breaks down the original query into component parts that can be executed independently across multiple databases, then aggregates the results. This segmentation allows parallel execution of sub-queries, significantly reducing total query execution time while maintaining data retrieval accuracy.
Solution Approach 2:
The patent introduces a query interface as an intermediary layer between the user and multiple databases. This interface manages the decomposition of queries, coordinates execution across data sources, and aggregates results. The intermediary handles the complexity of distributed querying, allowing users to submit single queries while the system manages multiple database interactions in the background.
2Reliability
If customer data is stored in separate databases for privacy and security reasons, then data security is improved, but query complexity increases
Solution Approach 1:
The query interface serves as an intermediary that abstracts the complexity of querying distributed databases. Users interact with a unified interface that handles query decomposition, execution coordination, and result aggregation. This intermediary layer maintains data security by keeping databases separate while eliminating query complexity for users, as they work with a single interface rather than managing multiple database connections.
Solution Approach 2:
The query interface provides universal functionality for accessing data across multiple databases through a single unified interface. It handles various query types, coordinates with different data sources, and presents consistent results. This multi-functional interface allows the system to maintain separate databases for security while providing users with a simple, unified access point that handles all query complexity internally.
3Loss of information
If multiple separate queries are issued to retrieve customer data, then comprehensive data retrieval is achieved, but the number of database connections and processing overhead increase
Solution Approach 1:
The system merges multiple separate query operations into a single coordinated execution plan. The query interface combines multiple sub-queries that would otherwise require separate database connections and processing steps. By merging these operations under unified management, the system retrieves comprehensive data while reducing processing overhead through coordinated execution and centralized result aggregation.
Solution Approach 2:
The query interface performs preliminary actions by pre-planning the decomposition and execution strategy before actually querying databases. It prepares the query structure, identifies required data sources, and organizes the execution plan in advance. This preliminary organization reduces processing overhead during actual execution, as the system already has a coordinated plan for retrieving comprehensive data across multiple sources.
Data Source
AI summary
An integrated asynchronous interface for data retrieval from across a plurality of data sources is described. An interface may include a plurality of Application Programming Interfaces (APIs) as well as a database for constructing responsive data. A search request may be decomposed at the interface to sub-search requests to be distributed to multiple data sources via a search request API. Data responsive to the sub-search requests may be aggregated at an interface database. A status API may maintain a status of the search request, and can update a tenant regarding the status of the tenant's search request. A response API may be used to provide reconstructed data responsive to the search request from the interface database to the tenant.