DistributedTracing
Following one request across multiple services/components via correlation/trace IDs.
Why we need this / what value this brings
Without it, following one request across multiple services means manually correlating logs by timestamp and guessing.
When to use this
Once a request genuinely spans more than one service — not useful (or necessary) within a single monolith.
How to use or implement this
Propagate a correlation/trace ID through every hop, and only invest in a full tracing backend (Jaeger, etc.) once there's more than one hop to trace.
Research questions
- Only matters once there's more than one hop — worth revisiting if/when Localz's backend splits.
Empty folder — drop notes, links, and findings here as you research.