Service Relationship Visualization in Distributed Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing technologies fail to provide a comprehensive visualization of relationships among multiple services in large-scale distributed processing systems, limiting the ability to identify bottlenecks and understand service interactions.
Innovation Solution
A method is developed to generate relation information by tracking communication between services, determining parent-child relationships based on communication timing, and outputting a relational chart to visually represent these relationships.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If comprehensive tracking of all service communications is performed to identify bottlenecks, then measurement precision is improved, but device complexity increases
Solution Approach 1:
The patent extracts and focuses only on the essential relationship data needed for bottleneck identification - specifically parent-child service relationships based on communication timing. By taking out only the critical timing information and relationship structures rather than tracking all communication details, the system achieves accurate bottleneck identification while reducing the complexity of data collection and processing infrastructure.
Solution Approach 2:
The patent segments the complex service communication data into hierarchical parent-child relationships. By dividing the overall service mesh into discrete parent-child pairs based on communication timing, the system can analyze bottlenecks at manageable relationship levels rather than attempting to process the entire service communication graph simultaneously, thus improving measurement precision without proportionally increasing device complexity.
2Loss of information
If detailed service relationship data is collected and processed, then information completeness is improved, but loss of time increases
Solution Approach 1:
The patent performs preliminary action by establishing parent-child relationships based on communication timing thresholds before detailed analysis is needed. By pre-defining relationships where the time difference between communication events falls within a predetermined threshold, the system prepares the relationship structure in advance, allowing for rapid bottleneck identification without requiring real-time processing of all service communication data, thus maintaining information completeness while reducing processing time loss.
3Ease of operation
If visualization of all service interactions is implemented, then ease of operation is improved, but device complexity increases
Solution Approach 1:
The patent extracts only the essential parent-child relationship information for visualization purposes, displaying the hierarchical service structure and communication flow without attempting to visualize every interaction detail. By taking out and displaying only the critical relationship hierarchy and timing-based parent-child connections, the system achieves clear and easy-to-understand service relationship visualization while avoiding the complexity of rendering complete service mesh interactions.
Data Source
AI summary
A method includes: generating relation information indicating service relationships each indicating that a first service and a source service and a destination service are related each other when a reception from the source service occurs at the first service and when a transmission to the destination service occurs at the first service and when a time of the reception is within a specific time period before a time of the transmission, determining whether the first service and the specified source service and the specified destination service have performed a related communication based on a number of service relationships corresponding to a combination of the first service and the specified source service and the specified destination service, and outputting information representing the combination of the first service and the specified source service and the specified destination service that are determined to have performed the related communication.


