Federated Data Management for Multi-Tenant Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Organizations face challenges in integrating data from diverse and disparate data stores, particularly after mergers or acquisitions, due to differences in data types and formats, which can be costly and burdensome when using data warehousing techniques.

Innovation Solution

Implementing a federated configuration data management system that supports multi-tenancy through configuration management database (CMDB) federation techniques, allowing for the execution of federated topology query language (FTQL) queries across multiple, geographically and technologically diverse data stores without requiring data duplication, using external data store adapters and a federation engine to manage data retrieval and access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data warehousing techniques are used to integrate data from diverse data stores, then data integration capability is improved, but cost and burden increase significantly

Engineering Contradiction:
Improvedata integration capabilityVSAvoidcost and burden
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent segments the data integration approach by using database federation techniques that allow data to remain in its original data stores rather than consolidating all data into a single data warehouse. This segmentation maintains data integration capability while reducing the burden of data movement and transformation across the entire dataset.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer (federation engine or virtualization layer) that enables data integration without physical data movement. This intermediary allows queries to access data across diverse data stores while the data remains in place, reducing the cost and burden associated with traditional data warehousing ETL processes.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If data is moved and transformed into data warehouse format, then data retrieval efficiency is improved, but the burden on the CMDB in terms of capacity and performance increases

Engineering Contradiction:
Improvedata retrieval efficiencyVSAvoidCMDB capacity and performance burden
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent extracts only the necessary data from external data stores on-demand through federation queries, rather than pre-loading all data into the CMDB. This extraction approach maintains data retrieval efficiency for required data while avoiding the capacity and performance burden of storing and managing large volumes of data in the CMDB.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent changes the dimension of data access by implementing a virtualization layer that provides logical data integration without physical data consolidation. This allows efficient data retrieval through unified queries while maintaining data in its original storage locations, thereby reducing CMDB capacity requirements.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Ease of operation

If large amounts of data are copied to the CMDB for integration, then data accessibility is improved, but the ability to integrate data from multiple external data stores is limited

Engineering Contradiction:
Improvedata accessibilityVSAvoidintegration of multiple external data stores
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent implements a universal federation engine that can access and integrate data from multiple diverse external data stores through a single unified interface. This multi-functional approach provides data accessibility comparable to data copying while vastly improving the ability to integrate data from numerous external sources without the limitations of physical data movement.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS10970300B2Supporting multi-tenancy in a federated data management system
Publication Date: 2021.04.06 MICRO FOCUS LLC
  • US10970300B2 patent drawing
  • US10970300B2 patent drawing
  • US10970300B2 patent drawing

AI summary

A system and method for supporting multi-tenancy in a federated data management system are provided herein. The method includes receiving a query from a client at a data management server, wherein the query includes a tenant property condition corresponding to the client. The method also includes identifying an external data store including data specified by the query and determining whether the external data store is multi-tenant enabled. The method further includes removing the tenant property condition and executing the query to retrieve the specified data if the external data store is not multi-tenant enabled.