The Art of Deploying Code Friday Night with Observability

The art and science of developing, deploying, and operating software are constantly in flux. Twenty-plus years ago, software was much more straightforward than what we have today. Most applications were built on simple clusters of HTTP servers, and looking for problems was only a log file away for developers. From monolith server processes to highly distributed and deep systems, we are now facing one of the toughest challenges in computing: truly understanding what our code is doing. One potential solution is distributed tracing. This technology allows developers to better understand their software and build a reasonable level of reliability that grants them the confidence to deploy software without much guesswork. Even on a Friday night!

0:00 Welcome
2:51 Understanding why distributed tracing is awesome
7:51 Applying distributed tracing to a Go microservice
10:03 Applying distributed tracing to a Java microservice
11:37 Using observability to compare software code releases
14:33 Historical traces retention with Elastic Observability
16:47 Integrate distributed tracing with monitoring is a great idea
21:41 Using distributed tracing with modern technology stacks
28:25 Propagating distributed tracing context in async architectures
34:20 Best practices to simplify your observability journey
40:42 Wrapping up

✅ Resources