Database Integration Flow Runtime Eliminates Data Conversion Overhead

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Enterprise Application Integration (EAI) solutions face high resource overhead and increased total cost of ownership due to multiple data format conversions and system boundary traversals when sending data between applications, using generic data exchange formats like XML and message-oriented middleware or Enterprise Service Bus systems.

Innovation Solution

Implementing application integration functionality directly on a relational database, where relational data is processed and transmitted without conversion to a generic data exchange format, leveraging database management system principles for high performance and scalability, and eliminating the need for a dedicated application server.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data is converted multiple times between database relational format and generic data exchange format (XML) and crosses multiple system boundaries, then application integration functionality is achieved, but resource overhead and total cost of ownership increase

Engineering Contradiction:
Improveapplication integration functionalityVSAvoidresource overhead
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent merges the database management system and application integration runtime into a single unified system. The database engine directly executes integration flows without requiring separate application servers or message-oriented middleware. This consolidation eliminates multiple system boundaries and data format conversions, reducing resource overhead while maintaining integration functionality.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent extracts the application integration runtime from traditional application servers and embeds it directly within the database management system. This extraction removes unnecessary intermediate layers and enables the database to directly process and transform data according to integration flow definitions, reducing the computational resources required for data conversion and transmission.

Inventive Principle:
Principle #2Taking out (Extraction)

2Adaptability or versatility

If multiple system boundaries are traversed and data is converted between formats, then application integration is achieved, but system complexity and total cost of ownership increase

Engineering Contradiction:
Improveapplication integrationVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent combines the database management system and application integration runtime into a single unified architecture. The database engine directly executes integration flows defined within the database, eliminating the need for separate application servers, message-oriented middleware, and Enterprise Service Bus components. This merger significantly reduces system complexity while maintaining full integration functionality.

Inventive Principle:
Principle #5Merging (Combining)

3Adaptability or versatility

If a dedicated application server is used for integration runtime, then integration functionality is provided, but total cost of ownership increases

Engineering Contradiction:
Improveintegration functionalityVSAvoidtotal cost of ownership
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent makes the database management system multi-functional by enabling it to directly execute application integration flows in addition to its traditional data storage and management functions. The database engine can process integration flows, transform data, and manage integration operations without requiring a dedicated application server. This universality eliminates the need for additional hardware and software investments, reducing total cost of ownership while maintaining integration functionality.

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

Data Source

PatentUS9740758B2Integration flow database runtime
Publication Date: 2017.08.22 SAP SE
  • US9740758B2 patent drawing
  • US9740758B2 patent drawing
  • US9740758B2 patent drawing

AI summary

The present disclosure describes methods, systems, and computer program products for providing application integration functionality directly on a relational database according to an implementation. One computer-implemented method includes inserting relational data into a start table of a database, detecting a change in the start table, retrieving the inserted relational data from the start table, processing, using a computer, the relational data using a database integration flow runtime into result data, inserting the result data into an end table of the database, detecting a change in the end table, and retrieving the result data from the end table.