Data Query Routing via Data Mesh for Multi-Version Datasets

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing technologies face challenges in efficiently managing queries for datasets with multiple versions across disparate databases, leading to increased processing time and potential inaccuracies due to inconsistent data versions.

Innovation Solution

The implementation of a data quantum paradigm within a data mesh, which allows for dynamic data query routing by identifying datasets and their versions through logical names rather than physical addresses, enabling loose coupling between applications and data sources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If applications use direct coupling to datasets with multiple versions across disparate databases, then data access flexibility is improved, but processing time increases and data consistency deteriorates

Engineering Contradiction:

Improvedata access flexibilityVSAvoidprocessing time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent introduces a data mesh layer as an intermediary between applications and disparate databases. This data mesh provides a unified logical view of multiple data versions across different databases, allowing applications to access data flexibly without directly querying multiple databases. The intermediary layer handles version resolution and data routing, reducing processing time while maintaining access flexibility.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the data access architecture into distinct layers: the application layer, the data mesh layer (with logical data structures), and the physical database layer. This segmentation allows each layer to operate independently, with the data mesh layer managing version control and routing logic, thereby improving processing efficiency without sacrificing adaptability.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If applications directly access multiple database versions, then data retrieval flexibility is improved, but data consistency and atomicity deteriorate

Engineering Contradiction:

Improvedata retrieval flexibilityVSAvoiddata consistency

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The data mesh acts as a mediator that ensures data consistency by providing a unified logical view of multiple versions. It manages version coherence and ensures atomicity of data operations across disparate databases, while still allowing flexible retrieval of different versions when needed.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a universal data access interface through the data mesh that handles multiple functions: version resolution, data routing, consistency management, and atomicity enforcement. This universal layer provides flexible data retrieval while maintaining reliability through centralized control of these critical functions.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Speed

If applications are strictly coupled to specific database versions, then processing speed is improved, but system adaptability and accuracy deteriorate

Engineering Contradiction:

Improveprocessing speedVSAvoidsystem adaptability

Core Design Contradiction:

SpeedVSAdaptability or versatility

Solution Approach 1:

The patent extracts the version management logic from the application layer and places it in the data mesh layer. Applications can maintain simple, fast processing logic while the data mesh handles complex version resolution and adaptability requirements, achieving both speed and system adaptability.

Inventive Principle:

Principle #2Taking out (Extraction)

4Adaptability or versatility

If applications query multiple databases for different data versions, then data availability is improved, but processing complexity and time increase

Engineering Contradiction:

Improvedata availabilityVSAvoidprocessing complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges multiple database queries into a unified data access interface through the data mesh. The data mesh consolidates data from disparate databases into a coherent logical structure, reducing processing complexity while maintaining data availability from multiple sources.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS12282468B2Dynamic data query routing for managing access to datasets having multiple versions

Publication Date: 2025.04.22 PAYPAL INC

AI summary

There are provided systems and methods for dynamic data query routing for managing access to datasets having multiple versions. A service provider, such as an electronic transaction processor for digital transactions, may provide data for different applications including local device-side software applications and web-based or server-side applications. The data may be read and provided within the application, for example, for output or processing, as well as operated on in the applications to update, add to, or delete from corresponding records. When retrieving or loading data, a data quantum may be used in a data mesh to abstract database physical locations and utilize logical names that allow for applications to code and query for data without direct entanglement with databases and corresponding stored datasets for the data. A router may then be used to route requests and queries for the data to optimized databases for the data.