Service Coordination via Distributed Data Exchange

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Service-oriented architectures (SOA) face bottlenecks in processing service requests due to centralized data exchange, which limits the efficiency of service coordination and execution in distributed computing environments.

Innovation Solution

A method and apparatus for coordinating service-oriented tasks by saving tasks as sequences of services, sending notifications for input and output locations between service providers, and receiving results, allowing for distributed operations without centralized information exchange, thereby improving task execution performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If centralized data exchange through ESB is used for service coordination, then service management and orchestration are simplified, but processing bottleneck and reduced execution speed occur

Engineering Contradiction:
Improveservice coordination complexityVSAvoidservice request processing speed
Core Design Contradiction:
Device complexityVSSpeed

Solution Approach 1:

The patent extracts the data exchange function from the centralized ESB and distributes it to service providers. Each service provider maintains its own data exchange capabilities, removing the bottleneck from the centralized architecture while maintaining coordination through a simplified registry-based approach.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The centralized ESB is segmented into distributed service providers, each handling its own data exchange independently. This segmentation eliminates the single-point bottleneck while maintaining service coordination through location-independent access to service outputs.

Inventive Principle:
Principle #1Segmentation

2Reliability

If all data requests and responses pass through ESB, then centralized control and management are achieved, but substantial bottleneck for processing service requests occurs

Engineering Contradiction:
Improvecentralized controlVSAvoidservice request processing throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system transitions from static centralized control to dynamic distributed coordination. Service providers dynamically exchange data directly based on service relationships registered in the location-independent registry, enabling parallel processing while maintaining control through service binding information.

Inventive Principle:
Principle #15Dynamics

3Ease of operation

If centralized information exchange is used, then service orchestration is simplified, but distributed operation efficiency is reduced

Engineering Contradiction:
Improveservice orchestration easeVSAvoidinformation exchange time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

Service binding information including data exchange locations is registered in advance in the location-independent registry. This preliminary action enables service providers to directly exchange data without real-time centralized coordination, reducing information exchange time while maintaining orchestration through pre-established service relationships.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9311612B2System and method for improved service oriented architecture
Publication Date: 2016.04.12 SAP SE
  • US9311612B2 patent drawing
  • US9311612B2 patent drawing
  • US9311612B2 patent drawing

AI summary

Certain embodiments enable improved execution of service-oriented tasks by coordinating service providers that access service-input values from other service providers and generate service-output values that are accessible by other service providers. Improved performance results from distributed operations of service providers that do not require centralized exchange of all information.