A real-time calling chain tracking method based on micro-service

Abstract

The invention discloses a real-time call chain tracking method based on micro-service. According to the method, a calling relation data structure is adopted, a distributed cache and database client monitoring are incorporated into a micro-service calling chain system, a trace ID is implanted into a business log, business information of a calling chain is connected in series, and the method is usedfor clearly sorting calling nesting relations one by one in complex calling. Through the system, the efficiency of positioning production problems can be greatly improved, and the understanding capability of development, operation and maintenance personnel on the system can be improved by analyzing the performance information of each link on the micro-service calling chain, so that the system canbe better optimized and improved.

Description

technical field [0001] The invention belongs to the technical field of communication, and relates to a microservice-based real-time call chain tracking method. Background technique [0002] At present, microservice has become a very popular term in IT Internet technology. The idea of ​​microservice architecture is to split the overall business into independent modules according to the business field. Each microservice module is deployed independently, and the relationship between microservices is loosely coupled. These characteristics of microservices predestined that the microservice architecture is inherently a distributed architecture, and the microservice modules interact through split interfaces and are stateless services. Under this architecture, a complete business process is likely to be processed and forwarded by multiple microservices. So in our daily business, we will encounter the following scenarios: [0003] 1. The user failed to place an order to purchase a...

AI Technical Summary

Problems solved by technology

[0003] 1. The user failed to place an order to purchase a certain product on a certain APP. Is it because the APP interface made a mistake in adjusting the CRM system, or the APP adjusted the counter system, or the APP adjusted the CRM system, and the CRM adjusted the counter incorrectly;

[0004] 2. When a user handles a certain business, there will always be a certain percentage of failures. Is there a problem with a certain node in a certain microservice cluster?

[0005] 3. In a certain microservice call, the access performance of the data layer is very poor. I want to know whether it is a problem with the performance of accessing the cache server (such as Redis) or the execution time of a certain SQL when accessing a relational database (such as MYSQL). too long?

However, Dapper only proposes a theoretical model and a simple implementation to solve the problem of request invocation. The function is relatively single and cannot provide a comprehensive solution.

Images