Thursday, February 18, 2021
Microservices are becoming mainstream now and the majority of new applications are developed using microservices architecture. But they throw some unique challenges around DevOps and Observability due to following:
- Rise of API ecosystem
- Application complexity is rising
- Applications are becoming more distributed
- Tech Stack is becoming broader and bigger everyday
- Hybrid and multi-cloud is becoming reality
- Monoliths to Microservices
Distributed Tracing, which is getting a lot of mindshare in the last few years is now becoming the new foundation of DevOps. Unlike traditional Application Performance Monitoring (APM), Distributed Tracing is intended to address the observability challenges and use-cases in the new microservices world.
eBPF advancement in Linux kernel brings whole new opportunities around kernel and application tracing. eBPF used in conjunction with distributed tracing unlock many interesting opportunities.
Eventually, Distributed Tracing will be a new APM, addressing MELT use-cases comprehensively (Metrics, Events, Logs and Traces). It is particularly well-suited to debugging and monitoring modern distributed software architectures, such as microservices. It helps pinpoint or isolate where failures occur and what causes sub-optimal performance.
It basically traces a network request as it travels through your services, as it would be in a microservices-based architecture. One of the main reasons you may want to do this is to troubleshoot or monitor the latency of a request as it travels through the different services.
In this talk, we will discuss Distributed Tracing and it’s various use cases in today’s cloud native world along with Demo of Distributed Tracing using some sample applications!
Download these images to your phone and post using the Instagram app.