Service Request Delegation in SOA Environments

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In service-oriented architecture (SOA) environments, calling services often waste computing resources by obtaining and transmitting unnecessary data, leading to inefficiencies in CPU cycles and network bandwidth usage, as they gather data that is not utilized by the called service.

Innovation Solution

Implementing a request delegation mechanism where the origin service delegates data collection to the recipient service, which stops data retrieval once unnecessary data is encountered, such as encountering a zero during a multiplication operation, allowing the recipient service to obtain only the required data needed for computation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the calling service obtains data from data sources before providing it to the called service, then the called service can process the data, but the calling service wastes computing resources (CPU cycles and network bandwidth) by obtaining and transmitting data that is not utilized by the called service

Engineering Contradiction:
Improvedata processing efficiencyVSAvoidCPU cycles and network bandwidth
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

Instead of the calling service obtaining data and passing it to the called service, the invention inverts the approach by allowing the called service to directly obtain data from data sources. This is achieved through delegation where the called service makes service calls directly to data providers, eliminating the intermediate step of data collection by the calling service and thus reducing wasted CPU cycles and network bandwidth.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The invention extracts the data collection function from the calling service and assigns it directly to the called service. The called service now directly interacts with data sources to obtain only the data it needs for processing, removing the unnecessary step where the calling service collects and transmits data that may not be fully utilized.

Inventive Principle:
Principle #2Taking out (Extraction)

2Productivity

If the calling service gathers a significant amount of data through multiple service calls, then the called service can perform computations, but unnecessary computing resources are expended in gathering and transmitting unused data

Engineering Contradiction:
Improvecomputation speedVSAvoidtime for data gathering and transmission
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The invention inverts the traditional data flow by allowing the called service to directly access data sources rather than receiving pre-collected data from the calling service. This enables the called service to obtain data on-demand and stop collection once sufficient data is gathered, eliminating time spent gathering and transmitting unused data while maintaining computation speed.

Inventive Principle:
Principle #13The other way round (Inversion)

3Productivity

If the recipient service obtains data directly through delegated requests, then only necessary data is collected and processing speed improves, but a request delegation mechanism must be implemented

Engineering Contradiction:
Improvecomputation speedVSAvoidrequest delegation mechanism
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The invention implements a universal request delegation mechanism that can be applied across different service types and data sources. The delegation framework provides standardized interfaces and protocols that work universally, allowing services to delegate data collection requests without requiring service-specific customizations, thus managing complexity through standardization.

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

Data Source

PatentUS9716772B1Request delegation in a service-oriented architecture environment
Publication Date: 2017.07.25 AMAZON TECH INC
  • US9716772B1 patent drawing
  • US9716772B1 patent drawing
  • US9716772B1 patent drawing

AI summary

Technologies are described herein for delegating requests in a service-oriented architecture (SOA) environment. A calling service in the SOA environment can delegate the task of obtaining data used in a computation to a called service that performs the computation. In order to delegate, the calling service may provide a request specification that defines a mechanism by which the called service can obtain the data. For example, the request specification might define a request to another service in the SOA for obtaining the data. The calling service might also provide an authentication ticket that can be utilized to confirm that the calling service has delegated the task to the called service. The called service can utilize the request specification and the authorization ticket to obtain the data. The obtained data may then be used to perform a computation. The results of the computation may then be provided to the calling service.