Pattern 49 / OPS
Use this when seeing where time and failures go across a distributed request.
Distributed Tracing fits when seeing where time and failures go across a distributed request. Mechanism: attach a trace id and record spans as the request crosses services. Use it for microservices, debugging latency, dependency maps, and incident response. The toll: sampling, context propagation, and cardinality must be managed.
Microservices, debugging latency, dependency maps, and incident response.
Checkout trace shows 600 ms spent in payment-service.
Describe the pressure first, then the mechanism, then the cost. That keeps the design grounded.
Same pressure family