Data Pipeline Configuration via Object-Oriented Metadata

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The high cost and complexity of configuring and maintaining data warehouses, especially in enterprise environments with multiple data types from different sources, make it challenging to efficiently process and manage large-scale data storage systems.

Innovation Solution

The automation of data pipeline system configuration and optimization using an object-oriented metadata model, which generates data flow logic packages programmatically and supports version control, rollback, and self-tuning, reducing the need for manual updates and minimizing the use of scripting tools.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If data warehouses are configured with ETL pipelines to process and manage raw data, then data processing capability is improved, but device complexity and maintenance cost increase

Engineering Contradiction:
Improvedata processing capabilityVSAvoidpipeline configuration complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system uses self-describing metadata that automatically generates pipeline configuration code, eliminating the need for manual expert configuration. The metadata contains all necessary information about data sources, transformations, and destinations, allowing the system to configure itself without human intervention.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Manual mechanical configuration by data warehousing experts is replaced with automated code generation from metadata. The system transforms high-level metadata descriptions into executable pipeline configuration code automatically, substituting human expertise with an automated generation process.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Adaptability or versatility

If data flow logic packages are manually updated to address changes in data stores, then adaptability is improved, but loss of time and productivity decrease

Engineering Contradiction:
Improveadaptability to data store changesVSAvoidmaintenance time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system automatically detects changes in data stores through metadata updates and regenerates the affected data flow logic packages without manual intervention. This self-service approach eliminates the time-consuming manual update process while maintaining full adaptability to changes.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The metadata is prepared in advance with complete information about data stores and their relationships. This preliminary preparation allows the system to quickly generate and update pipeline configurations when changes occur, avoiding time-consuming ad-hoc configuration work.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If data warehouses are carefully configured before accepting incoming data, then reliability is improved, but device complexity and cost increase

Engineering Contradiction:
Improvedata processing reliabilityVSAvoidconfiguration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system automatically generates reliable pipeline configurations from self-describing metadata, eliminating the need for complex manual configuration while maintaining reliability. The metadata inherently contains all necessary information for correct pipeline setup, and the automated generation process ensures consistency and accuracy.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9396037B2Model-based data pipeline system optimization
Publication Date: 2016.07.19 MICROSOFT TECHNOLOGY LICENSING LLC
  • US9396037B2 patent drawing
  • US9396037B2 patent drawing
  • US9396037B2 patent drawing

AI summary

A computer-implemented method for optimizing a data pipeline system includes processing a data pipeline configuration manifest to generate a framework of the data pipeline system and a data flow logic package of the data pipeline system. The data pipeline configuration manifest includes an object-oriented metadata model of the data pipeline system. The computer-implemented method further includes monitoring performance of the data pipeline system during execution of the data flow logic package to obtain a performance metric for the data pipeline system, and modifying, with a processor, the framework of the data pipeline system based on the data pipeline configuration manifest and the performance metric.