Data Integration Framework Abstracting Processing Constructs

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data integration tools, such as proprietary ETL tools, create vendor lock-in situations, reduce developer productivity, and increase licensing costs, while being misaligned with application toolchains, affecting quality assurance and modernization efforts in data warehousing.

Innovation Solution

A data integration framework module that abstracts data processing constructs into user-friendly templates, enabling developers to define and test data transformations independently, thereby eliminating the need for language-level object instantiation and reducing reliance on proprietary tools.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If proprietary ETL tools are used for data integration, then data processing functionality is provided, but vendor lock-in occurs and licensing costs increase

Engineering Contradiction:
Improvedata processing functionalityVSAvoidvendor lock-in
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces an open-source data integration framework as an intermediary layer between data sources and data processing applications. This framework provides standardized connectors and transformation capabilities, enabling organizations to avoid direct dependence on proprietary ETL tools while maintaining robust data processing functionality. The framework acts as a mediator that decouples the organization from vendor-specific implementations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The framework implements universal data processing capabilities that can handle multiple data sources, formats, and transformation scenarios through a single platform. By providing a comprehensive suite of connectors, transformation functions, and scheduling capabilities, the framework eliminates the need for multiple vendor-specific tools, thereby reducing licensing costs and avoiding vendor lock-in while maintaining reliable data processing.

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

2Reliability

If proprietary ETL tools are used, then data integration capabilities are provided, but developer productivity decreases due to complex instantiation processes

Engineering Contradiction:
Improvedata integration capabilitiesVSAvoiddeveloper productivity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The framework enables self-service data integration through drag-and-drop interface components and automated code generation. Developers can configure data pipelines using visual templates and predefined transformation patterns, eliminating the need for manual instantiation of complex language-level objects. The system automatically generates the necessary code and configurations, significantly reducing development time and complexity while maintaining robust data integration capabilities.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The framework provides pre-configured connectors, transformation templates, and best-practice patterns that can be directly applied to common data integration scenarios. By having these components prepared in advance, developers avoid the time-consuming process of building data pipelines from scratch or manually configuring complex instantiation parameters, thereby improving productivity without compromising integration capabilities.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If vendor-based data processing products are used, then data integration functionality is provided, but time to market increases

Engineering Contradiction:
Improvedata integration functionalityVSAvoidtime to market
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The framework includes a library of reusable data integration patterns, transformation templates, and connector implementations that can be copied and adapted for new projects. Instead of developing data integration solutions from scratch using proprietary tools, organizations can leverage these pre-built components, significantly reducing development time while maintaining reliable and proven data integration functionality.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The framework provides pre-configured data pipelines, transformation logic, and integration patterns that are prepared in advance for common scenarios. This preliminary preparation allows organizations to rapidly deploy data integration solutions by simply configuring specific parameters rather than building entire pipelines, thereby reducing time to market while ensuring functional reliability through tested and validated patterns.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11436134B2Method and apparatus for data integration framework
Publication Date: 2022.09.06 JPMORGAN CHASE BANK NA
  • US11436134B2 patent drawing
  • US11436134B2 patent drawing
  • US11436134B2 patent drawing

AI summary

Various methods, apparatuses/systems, and media for integrating data are provided. A processor implements a data processing framework configured to run native on a big data platform and abstracts data processing constructs to a user friendly template, thereby eliminating necessity of user initiated tasks of instantiating language level objects. The processor also implements a core set of data pipeline configurations on the template configured to initiate a chain of user defined data transformations. A receiver operatively connected with the processor via a communication network receives input of the chain of the user defined data transformations. The processor tests each transformation independently of each other and outputs data integration solutions on the big data platform based on a positive test result.