Unified Database Management Layer for Heterogeneous Systems

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current database management systems struggle to efficiently manage and process requests across diverse database environments, including traditional relational and alternate data processing systems, due to differences in capabilities, data representation, and interfaces, which limits their ability to operate cohesively and optimize query performance.

Innovation Solution

A database unifying system that connects and coordinates multiple database systems by recognizing and leveraging their differences, using links to access and process requests across systems with varying capabilities, data representations, and interfaces, effectively treating them as a unified database environment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple database systems with different capabilities, data representations, and interfaces are integrated into a unified environment, then the system's adaptability and versatility improve, but the device complexity increases

Engineering Contradiction:

Improveability to process requests across diverse database environmentsVSAvoidcomplexity of managing heterogeneous database systems

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a unifying database management layer that acts as an intermediary between the user and multiple heterogeneous database systems. This mediator translates user requests into system-specific operations, handles data representation differences, and manages interface variations, thereby enabling unified access without requiring users to directly manage the complexity of each individual database system.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The database management system implements universal interfaces and standardized data representation layers that work across all connected database systems. By creating a multi-functional framework that can handle relational, non-relational, and other specialized database types through common protocols and abstraction layers, the system achieves versatility without proportionally increasing operational complexity.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Ease of operation

If a unifying database system coordinates multiple heterogeneous systems, then the ease of operation improves, but the device complexity increases

Engineering Contradiction:

Improveease of accessing data across multiple database systemsVSAvoidcomplexity of the coordination and link management system

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The patent segments the database management architecture into distinct functional layers: a user-facing unified interface layer, a translation and coordination layer that handles system-specific protocols, and the underlying heterogeneous database systems. This segmentation allows the complexity to be isolated in the middle layer while maintaining simplicity at the user interface and in the individual database systems themselves.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

A coordination layer serves as an intermediary that manages links between the unified system and multiple database systems. This mediator handles the complexity of cross-system operations, data format conversions, and protocol translations, thereby shielding users from operational complexity while enabling seamless access across heterogeneous systems.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Productivity

If database requests are processed by selecting from multiple system resources, then the productivity improves, but the measurement precision of system capabilities increases

Engineering Contradiction:

Improvequery processing efficiency across database systemsVSAvoiddifficulty of assessing differences between database capabilities

Core Design Contradiction:

ProductivityVSDifficulty of detecting and measuring

Solution Approach 1:

The system implements capability detection and assessment mechanisms that provide feedback about the features, performance characteristics, and limitations of each connected database system. This feedback loop enables the unifying management layer to make informed decisions about query routing and resource selection, optimizing productivity while systematically managing the complexity of capability assessment through automated discovery and characterization.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS9805121B2Management of different database systems and/or environments

Publication Date: 2017.10.31 TERADATA CORP

AI summary

A database request can be processed at least partly based on one or more differences between multiple database systems and/or environments. The differences can, for example, include differences between one or more database capabilities respectively provided by the multiple database systems, differences between the representation of data in the multiple database systems, and differences in the interfaces for accessing the multiple database systems.