Expandable ETL Framework with Configuration-Driven External Transformations

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing ETL frameworks require developers to write custom code for each operation, lacking flexibility and expandability to perform new data transformations without modifying the framework.

Innovation Solution

An ETL framework that includes reusable modules and configuration files to execute new data transformations via external command data, such as SQL statements, allowing integration of external modules without altering the framework's native properties.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If developers write custom code for each ETL operation, then the framework can perform specific data transformations, but the framework lacks flexibility and expandability for new transformations

Engineering Contradiction:
Improveflexibility and expandabilityVSAvoidcustom coding requirements
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent uses configuration files as templates or blueprints that define ETL operations. Instead of writing custom code for each transformation, developers create configuration files that specify data sources, transformations, and destinations. The ETL framework then executes these configurations, allowing new transformations to be added simply by creating new configuration files rather than modifying the framework itself.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent enables dynamic modification of ETL behavior through configuration parameters. By changing values in configuration files (such as data source paths, transformation rules, and destination specifications), the system can perform different data transformations without code changes. This parameter-driven approach provides flexibility while maintaining a stable framework core.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If the framework is modified to support new data transformations, then new capabilities are added, but the core framework structure changes

Engineering Contradiction:
Improvenew data transformation capabilitiesVSAvoidframework core structure
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The patent separates the ETL system into two distinct layers: a stable core framework that provides execution infrastructure, and configurable operation definitions that specify individual ETL tasks. This segmentation allows new transformations to be defined in configuration files without modifying the framework core, maintaining structural stability while enabling new capabilities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces configuration files as an intermediary layer between the framework core and specific ETL operations. This intermediary allows the framework to execute new transformations by loading and processing configuration definitions, without requiring changes to the framework's core structure. The configuration files act as a buffer that enables adaptability while preserving framework stability.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If developer tools provide ETL functionality, then data can be moved and transformed, but teams must write code for each operation reducing efficiency

Engineering Contradiction:
ImproveETL operation efficiencyVSAvoidcoding effort
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent enables self-service ETL operations through configuration files. Instead of requiring developers to write and maintain custom code for each ETL task, the system allows operations to be defined and executed through configuration specifications. This reduces the coding burden and allows business users or analysts to potentially define their own ETL operations without programming expertise.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces the mechanical process of writing and executing custom code with a configuration-driven approach. Configuration files serve as a higher-level abstraction that the framework translates into executable ETL operations. This substitution eliminates the need for manual coding while maintaining full ETL functionality, significantly improving productivity and ease of operation.

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

Data Source

PatentUS12353428B2System and method for expanding a data transfer framework
Publication Date: 2025.07.08 THE TORONTO DOMINION BANK
  • US12353428B2 patent drawing
  • US12353428B2 patent drawing
  • US12353428B2 patent drawing

AI summary

Apparatus and methods for expanding a data transfer framework are disclosed. Exemplary implementations may: provide an ETL framework comprising a plurality of ETL modules and comprising code including variables; obtain a configuration file including data values to replace the variables for executing selected ETL modules, and including external command data configured to execute a new data transformation external to and absent from the ETL framework, the external command data including a reference to an external module generated in relation to an external interface; and execute the one or more selected ETL modules based on the code, the data values and the external command data. Exemplary implementations provide a flexible and expandable ETL framework that enable a new type of data transformation that is not currently supported by the framework, without having to modify the framework. The framework may impart native properties and characteristics of the framework to the external module.