SOA Data Exchange Orchestration via ESB and Direct Channels

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Service Oriented Architecture (SOA) systems experience performance delays and inefficiencies in data exchanges and synchronizations due to reliance on Enterprise Service Bus (ESB) for all data exchanges, necessitating improved methods for managing data across multiple repositories.

Innovation Solution

Implementing a system where instructions for data exchange are transmitted via an ESB or other Message Oriented Middleware (MOM) or Event Driven Architecture (EDA), while the data exchange itself occurs through channels other than the ESB, such as hardware buses, broadcasts, or multicasts, allowing for orchestrated data exchanges and synchronizations between multiple data repositories.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all data exchanges pass through the Enterprise Service Bus (ESB) in SOA systems, then centralized control and orchestration are achieved, but performance delays and inefficiencies occur

Engineering Contradiction:
Improvecentralized controlVSAvoiddata exchange performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments data exchange into two distinct parts: control instructions exchanged via ESB and actual data exchanged via direct channels between repositories. This separation allows centralized orchestration through the ESB while enabling high-performance direct data transfer, resolving the contradiction between centralized control and exchange performance.

Inventive Principle:
Principle #1Segmentation

2Device complexity

If data exchange instructions and data are transmitted through the same ESB channel, then simplified architecture is maintained, but performance and efficiency deteriorate

Engineering Contradiction:
Improvearchitecture simplicityVSAvoiddata exchange efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent introduces a dimensional separation by establishing dual communication paths: one dimension for control instructions (via ESB) and another dimension for data transfer (via direct repository channels). This multi-dimensional approach maintains architectural simplicity in control while achieving high efficiency in data exchange.

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

Data Source

PatentUS9535769B2Orchestrated data exchange and synchronization between data repositories
Publication Date: 2017.01.03 ORACLE INT CORP
  • US9535769B2 patent drawing
  • US9535769B2 patent drawing
  • US9535769B2 patent drawing

AI summary

Embodiments of the invention provide systems and methods for providing efficient Service Oriented Architecture (SOA) orchestrated data exchanges and synchronizations between a plurality of databases or other repositories. According to one embodiment, a method of exchanging data between a plurality of data repositories can comprise distinguishing instructions to perform a data exchange from data of the data exchange. The instructions to perform the data exchange can be exchanged via an Enterprise Service Bus (ESB) of a Service Oriented Architecture (SOA) and the data of the data exchange between two or more of the plurality of data repositories can be exchanged via a channel other than the ESB. The data exchange can be orchestrated by orchestrating the instructions to perform the data exchange.