With distributed tracing in place inside our application based on microservices architecture, we have enabled a lot of power to tackle quite some use cases, such as the following:

• Understanding the flow of the application: With distributed tracing, we can now visualize how an incoming request from the client flows inside our application from one service to another. This kind of information is really useful in figuring out how the application works and to enable better testing of the application.
• Narrowing down the bugs: With the idea of how the request goes from one service to another, we can quickly isolate the services that may be causing the request to produce an incorrect response by analysing what steps were taken by which service to process the request before a response was generated.
• Finding performance bottlenecks: With timing visualization in place for how long a particular step took in the request-response cycle, we can now quickly analyse which part of the application is causing a performance bottleneck in the request-response cycle, hence allowing us to solve the issue with ease.

With all of this knowledge, we can now efficiently build, test, and deploy our applications based upon the microservices architecture, while also allowing for a more matured process to manage the infrastructure that powers our application.