dubbo service link tracking

At present, many businesses use micro-service architecture. There are two ways to divide service modules:

Service Function Division

Business Division

Either way, an interface call requires multiple services to be completed in collaboration. A service problem will lead to failure. Although there are artifact architectures such as logback + kafka + ELK, the positioning problem is also troublesome. If a unique ID (traceId) can be used to track the book throughout the link. With this service call, you can find the current traceId in the ELK to locate the problem.

I. Cases

1. Case structure

pratices-demo-provider-core: Defining service interfaces

pratices-demo-provider: implementation

pratices-demo-consumer-core: service consumers and service providers

pratices-demo-consumer: implementation

pratices-demo-web: providing http services

pratices-demo-trace: the core module of this case, intercepts service invocation, sets traceId, and tracks this service invocation