Queue-Based Dependency Tracking in Virtual Machine Service Buses

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In distributed virtual machine environments, identifying application program dependencies is challenging due to performance degradation or failure, especially in queue-based systems, where load balance and high availability require accurate dependency information to maintain service quality and customer satisfaction.

Innovation Solution

A method and system for generating queue-based application dependencies in virtual machines, involving intercepting messages via an enterprise service bus, filtering to identify request messages, calculating checksums for message identification, and recording client-server relationships in a dependencies table, allowing for tracking of application trajectories.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If distributed application systems are used to achieve load balance and high availability, then service reliability is improved, but dependency tracking becomes more difficult and complex

Engineering Contradiction:
Improveservice reliabilityVSAvoiddependency tracking complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an enterprise service bus (ESB) as an intermediary component that mediates all communication between application programs. The ESB intercepts and manages messages, providing a centralized point for dependency tracking. This mediator approach simplifies the complex web of direct application-to-application dependencies by routing all interactions through a controlled intermediary that can record and analyze communication patterns.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback mechanisms by continuously monitoring messages transmitted through the ESB and recording dependency relationships in a dependencies table. This feedback loop allows the system to automatically track and update dependency information based on actual runtime communication patterns, enabling dynamic adaptation to changing service relationships while maintaining reliability.

Inventive Principle:
Principle #23Feedback

2Measurement precision

If message interception and filtering is performed to track dependencies, then dependency identification accuracy is improved, but system processing overhead increases

Engineering Contradiction:
Improvedependency identification accuracyVSAvoidprocessing overhead
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent extracts only the essential and relevant information from intercepted messages for dependency tracking purposes. Instead of analyzing complete message contents, the system extracts key elements such as message type, source application, destination application, and message identification. This extraction approach maintains high dependency identification accuracy while minimizing processing overhead by focusing only on critical data points.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system applies partial action by selectively intercepting and processing only request messages rather than all message types. Reply and other non-request messages are excluded from detailed dependency analysis. This partial processing approach reduces the volume of data requiring analysis while still capturing sufficient information to accurately identify dependency relationships.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10210031B2Method and system for generating queue based applications dependencies in virtual machines
Publication Date: 2019.02.19 IND TECH RES INST
  • US10210031B2 patent drawing
  • US10210031B2 patent drawing
  • US10210031B2 patent drawing

AI summary

A method and a system for generating queue based applications dependencies in virtual machines are provided. The method includes the following steps. At least one transmitting message transmitted via at least one enterprise service bus by a plurality of application programs is intercepted. The at least one transmitting message includes at least one request message. The at least one request message is obtained by filtering the at least one transmitting message. A client and a server of each of the at least one request message are obtained. A checksum of each of the at least one request message is calculated to obtain a message identification of each of the at least one request message. The client, the server and the message identification of each of the at least one request message are recorded in a dependencies table.