Microservice Call Tracking via Embedded Intermediary
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In microservice architectures, it is challenging to obtain call information between multiple microservices, especially when there are many, due to their loosely coupled nature and the use of RESTful APIs based on HTTP protocols.
Innovation Solution
Implementing a method and system that monitors microservice requests, determines call relationships between microservices, and generates call information using a tracking component within each microservice, which includes a monitoring module, a relationship determining module, and a call information generation module to track and display metadata for call relationships and indicator values.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If microservices are designed with loose coupling and RESTful APIs for independence and flexibility, then adaptability and ease of operation are improved, but the ability to obtain and track call information between microservices deteriorates
Solution Approach 1:
The patent introduces a tracking component as an intermediary that is embedded within each microservice. This component intercepts and captures metadata from outgoing microservice requests, including caller information, called service information, and interface details. The tracking component acts as a mediator between the loosely coupled microservices, enabling call information collection without disrupting the independent RESTful communication between services.
2Ease of operation
If microservices operate independently with minimal coupling, then ease of operation and maintenance are improved, but device complexity for tracking and managing call relationships worsens
Solution Approach 1:
The tracking system is segmented and distributed across multiple microservices rather than being centralized. Each microservice contains its own tracking component that independently captures and manages its own call metadata. This segmentation allows each microservice to operate independently while the collective tracking components form a distributed tracking network, reducing the complexity burden on any single service.
3Measurement precision
If metadata collection is implemented in each microservice to track call relationships, then measurement precision of call information is improved, but use of energy and processing resources worsens
Solution Approach 1:
The tracking component extracts only the essential metadata from microservice requests, such as caller identification, called service identification, and interface information. Rather than capturing or processing the entire request payload, the system extracts only the necessary call relationship information, reducing the processing overhead while maintaining accurate tracking of inter-service dependencies.
Data Source
AI summary
Implementations of embodiments disclose an information processing method, apparatus, and system. In an embodiment, the information processing method includes: monitoring at least one microservice request sent by each of at least two microservices, a microservice request being used by one microservice to call another microservice; determining a call relationship between a first microservice and a second microservice from each detected microservice request, the first microservice being a microservice sending the microservice request, and the second microservice being a microservice that the microservice request requests to call; and generating call information between the at least two microservices based on all determined call relationships. In embodiments of the present invention, call information between microservices can be obtained, the obtained call information is visually displayed to intuitively and conveniently present dependence between the microservices, and a processing capability of a microservice can be adjusted based on an indicator value.