Multi-Tenant Analytics Pipelines With Metadata-Driven Tenancy Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data analytics platforms are limited by their architecture, requiring technical expertise, segregating data, lacking scalability and security, and failing to provide integrated insights across multiple data products.

Innovation Solution

A serverless data analytics platform that automates deployment and scaling, uses metadata-driven flows, and supports flexible access controls to enable less-technical users to gain insights across multiple data products.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If existing data analytics platforms use traditional architecture with physical infrastructure, then data processing capability is provided, but scalability is limited and resource requirements are high

Engineering Contradiction:
ImprovescalabilityVSAvoidresource requirements
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The system implements automated metadata extraction and flow generation that enables the platform to self-configure data processing pipelines without manual intervention. The metadata service automatically discovers data characteristics and generates appropriate processing flows, eliminating the need for technical specialists to manually configure each data product pipeline.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The platform dynamically adjusts processing parameters based on metadata characteristics. By analyzing metadata properties such as data type, volume, and structure, the system automatically configures optimal processing parameters for each data product, enabling scalable resource utilization without fixed infrastructure commitments.

Inventive Principle:
Principle #35Parameter changes

2Ease of operation

If existing platforms require technical specialists to manage data extraction and loading, then data processing is performed, but ease of operation deteriorates and technical expertise is required

Engineering Contradiction:
Improveease of operationVSAvoidtechnical expertise required
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The metadata-driven automation system performs data extraction, transformation, and loading operations automatically based on metadata specifications. Users simply define their data processing needs at a high level, and the system self-configures the complete data pipeline including extraction from sources, transformation logic, and loading to destinations without requiring users to understand underlying technical complexities.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The metadata service acts as an intermediary layer between users and the complex data processing infrastructure. It translates high-level user requirements into detailed processing configurations, shielding users from technical complexity while enabling sophisticated data processing capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of information

If existing platforms segregate data into separate data products, then data storage is organized, but the ability to gain integrated insights across multiple data products deteriorates

Engineering Contradiction:
Improveintegrated insightsVSAvoiddata architecture complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The metadata-driven flow engine provides a universal processing framework that handles multiple data products through a single unified system. Rather than requiring separate processing infrastructure for each data product, the same metadata service and flow generation mechanism serves all data products, enabling integrated insights while maintaining organizational separation through logical rather than physical segmentation.

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

Solution Approach 2:

The system merges the processing logic for multiple data products into a unified metadata-driven framework. By combining the metadata extraction, flow generation, and execution capabilities into a single service, the platform enables cross-data product analytics while maintaining the organizational boundaries of individual data products through metadata-based access control.

Inventive Principle:
Principle #5Merging (Combining)

4Productivity

If existing platforms lack automation in data management, then manual control is maintained, but productivity deteriorates and technical support requirements increase

Engineering Contradiction:
ImproveproductivityVSAvoidautomation level
Core Design Contradiction:
ProductivityVSExtent of automation

Solution Approach 1:

The metadata service implements self-service automation that automatically discovers data characteristics, generates processing flows, and configures data pipelines without human intervention. This automation dramatically increases productivity by eliminating manual configuration tasks while the system self-manages the complexity of coordinating multiple data products and processing operations.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12536181B2Systems and methods for management of multi-tenancy data analytics platforms
Publication Date: 2026.01.27 FIDELITY INFORMATION SERVICES LLC
  • US12536181B2 patent drawing
  • US12536181B2 patent drawing
  • US12536181B2 patent drawing

AI summary

A data analytics system configured to perform operations is disclosed. The operations can include creating, in response to instructions received from a user, a first pipeline. This pipeline can be configured to extract data from an append-only first data store, extract identifying characteristics from the extracted data, provide the identifying characteristics to an identity service, and receive a tenancy identifier from the identity service. The pipeline can further be configured to create a data object in a second data store using the extracted data; create a tenancy object in a metadata store, the tenancy object associated with the data object, the metadata store implementing a hierarchical data object ownership graph; and associate the tenancy object with a parent object in the hierarchical data object ownership graph. The data analytics system can then tear down the first pipeline.