SOA Message Characterization for Dependency Tracking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In service-oriented architecture (SOA)-based systems, managing and monitoring transactions is challenging due to difficulties in identifying participating services, which hinders root-cause failure analysis, performance analysis, and diagnostics, and altering messages to track dependencies can lead to security issues and failures with external services.

Innovation Solution

A system that characterizes messages to determine dependencies between services without altering them, using characterization values computed from message contents, which are then stored and compared to identify equivalent messages and establish dependency links, facilitating the management of transactions and services within the SOA-based network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Difficulty of detecting and measuring

If messages are altered to insert tracking keys, then dependency tracking capability is improved, but message security and external service compatibility deteriorate

Engineering Contradiction:
Improvedependency tracking capabilityVSAvoidmessage security and external service compatibility
Core Design Contradiction:
Difficulty of detecting and measuringVSReliability

Solution Approach 1:

The patent introduces an intermediary mechanism (message observer or proxy) that intercepts messages before they reach external services. This intermediary extracts necessary information for dependency tracking without modifying the original messages, thereby maintaining message security and external service compatibility while still enabling dependency tracking through characterization values computed from message contents

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

Instead of altering original messages, the patent creates copies or representations of message contents in the form of characterization values. These characterization values capture essential message properties for tracking dependencies without modifying the actual messages that need to be transmitted securely to external services

Inventive Principle:
Principle #26Copying

2Measurement precision

If message contents are fully analyzed to identify dependencies, then dependency detection accuracy is improved, but computational overhead increases

Engineering Contradiction:
Improvedependency detection accuracyVSAvoidcomputational overhead
Core Design Contradiction:
Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The patent extracts only the essential characteristics needed for dependency tracking from complete message contents. By identifying and extracting specific message properties (such as message type, operation, or key identifiers) rather than analyzing entire message payloads, the system achieves sufficient dependency detection accuracy while significantly reducing computational overhead

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent transforms variable-length message contents into fixed-size characterization values through hashing or encoding functions. This parameter transformation maintains the ability to identify equivalent messages for dependency tracking while reducing the computational complexity of comparing and storing dependency information

Inventive Principle:
Principle #35Parameter changes

3Speed

If characterization data is stored externally to messages, then message processing speed is improved, but system complexity increases

Engineering Contradiction:
Improvemessage processing speedVSAvoidsystem complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent merges the characterization value computation and storage functionality into existing message infrastructure components (such as message queues, event streams, or logging systems). By integrating dependency tracking data with existing message processing pipelines rather than creating separate external storage systems, the approach improves processing speed while minimizing additional system complexity

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS8195789B2System, apparatus and method for characterizing messages to discover dependencies of services in service-oriented architectures
Publication Date: 2012.06.05 ORACLE INT CORP
  • US8195789B2 patent drawing
  • US8195789B2 patent drawing
  • US8195789B2 patent drawing

AI summary

A system, apparatus, computer readable medium and method are disclosed for identifying underlying services of transactions in a service-oriented architecture (“SOA”)-based computer network. In one embodiment, a computer readable medium includes executable instructions to characterize messages communicating among services to form characterizations of the messages. Also included are executable instructions to determine dependencies using the characterizations of messages within a subset of the services. These dependencies can be represented as dependency links interconnecting the subset of the services that effectuate a transaction of interest. By identifying the dependency links, the underlying services in SOA-based networked computer system can advantageously be determined for managing the behavior of the subset of the services and other distributed services of the SOA-based networked computer system.