Parallel Execution Points in Integration Orchestration Flows

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Integration orchestration platforms, such as iPaaS, execute independent I/O-based activities serially, failing to utilize parallel processing capabilities, which leads to suboptimal runtime performance during integration flows.

Innovation Solution

The method determines points of parallel execution within an integration flow by identifying when all preconditions are met and input elements are ready, inserting hidden activities to execute certain connectors asynchronously, allowing independent I/O activities to run in parallel without disrupting sequential processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If independent I/O-based activities are executed serially in integration orchestration, then sequential processing is maintained, but runtime performance is suboptimal

Engineering Contradiction:
Improveruntime performanceVSAvoidprocessing time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The integration orchestration is segmented into independent executable units called activities. The system identifies independent I/O-based activities that can be executed in parallel by analyzing activity dependencies and inserting parallel execution points, thereby transforming sequential execution into parallel execution while maintaining data flow integrity

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system transitions from one-dimensional sequential execution to multi-dimensional parallel execution by introducing temporal dimensionality. Independent activities are dispatched to run concurrently in different execution threads, utilizing parallel processing capabilities to improve runtime performance without compromising sequential processing requirements

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Loss of time

If parallel execution is implemented, then processing time is reduced, but system complexity increases

Engineering Contradiction:
Improveprocessing timeVSAvoidorchestration complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The system introduces intermediary components including parallel execution points, activity dependency graphs, and execution context managers. These intermediaries automatically manage the complexity of parallel execution by handling thread coordination, dependency resolution, and data flow management, allowing parallel processing without exposing complexity to users

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The integration orchestration platform automatically analyzes activity dependencies, identifies parallel execution opportunities, and inserts parallel execution points without user intervention. The system self-manages the complexity of parallel execution by autonomously determining which activities can run concurrently and coordinating their execution

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11381638B1System and method for parallel execution of activites in an integration flow
Publication Date: 2022.07.05 ORACLE INT CORP
  • US11381638B1 patent drawing
  • US11381638B1 patent drawing
  • US11381638B1 patent drawing

AI summary

Systems and methods for parallel execution of activities in an integration flow. Systems and methods are provided for determining one or more points within an integration orchestration where downstream activities can be executed in parallel and/or asynchronously with the main flow of the integration orchestration.