Federated Database Manager Plug-in Architecture for New Data Sources

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current Business Intelligence (BI) tools face challenges in supporting new data sources efficiently, as existing solutions primarily focus on connectivity rather than leveraging analytic capabilities, requiring substantial code modifications and new versions for adding data sources to federated databases.

Innovation Solution

A plug-in architecture for federated databases that allows adding new data sources without rewriting the federated database manager software, using data source cartridges that provide metadata and generate physical queries, enabling the analytics engine to integrate new data sources into the logical model.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional federated database manager code is used, then existing data sources can be queried, but new data sources cannot be added without modifying the core software code

Engineering Contradiction:

Improveability to support new data sourcesVSAvoidsoftware code modification requirement

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the federated database manager into distinct functional components: a core engine that remains unchanged and executable cartridges that handle specific data source types. This segmentation allows new data sources to be added via cartridges without modifying the core software code, resolving the contradiction between adaptability and code complexity.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces cartridges as intermediary components between the federated database manager and data sources. These cartridges act as mediators that translate between the core engine's generic queries and data source-specific protocols, enabling new data sources to be integrated without direct modifications to the core manager code.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If API-based connectivity is provided for new data sources, then connection is enabled, but analytic capabilities of BI tools cannot be leveraged

Engineering Contradiction:

Improvedata source connectivityVSAvoidanalytic capability utilization

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The cartridge architecture provides a universal interface that simultaneously handles both connectivity and analytic capabilities. The cartridges are designed to work with the federated database manager's query optimization and analysis engines, enabling BI tools to leverage their full analytic potential across diverse data sources through a single unified mechanism.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS10108744B2Administrative tool and physical execution plan interface for plug-in architecture of business intelligence platform using data source cartridges

Publication Date: 2018.10.23 ORACLE INT CORP

AI summary

Embodiments implement a plug-in architecture supporting adding new data sources to a legacy federated database without the need to recode a federated database manager software module. The federated database manager software module includes an administrative tool and a plug-in framework for interfacing with a data source cartridge. The data source cartridge supplies metadata including a feature table of a newly added data source to the framework and creates a physical query for the newly added data source based on an execution plan generated by the federated database manager software module. The administrative tool generates presentation panes including new data sources added to the legacy federated database.