Lightning Talks
summary
Automatic compile-time instrumentation using Orchestrion injects tracing, logs and profiling into a Go binary by running go build with a special flag and immediately sends traces to Datadog; demo shows logs and traces appearing with no source changes. A short compilers segment argues tail-call optimization is avoided because it breaks runtime/backtrace and perf-based profiling and is hard to implement portably with little perf gain. A live code demo builds a CRUD API with generics, GORM and rest in peace in under 50 LOC, runs on :5555 and successfully serves list and modify endpoints.
AI-written summary · about
chapters (5)
- 0:00Introduction to talk
- 0:27Instrumenting Go with Orest
- 5:13Why no TCO in Go
- 10:33Live coding REST in Peace
- 16:05Q&A and closing
related talks
43mAutomatically Instrument Your Go Source Code with Orchestrion
22mDynamic Go Instrumentation for Production Environments
30mLightining Talks
51mGo Tooling in Action
30mDynamically Instrumenting Go Programs
01h 08mLightning Talks Day 2
30mMastering Distributed Tracing with Go
20mStrategies for Auto-Instrumenting Go Applications Without Code Changes