Design a Distributed Tracing System
Distributed tracing follows one user request as it moves through a system. A click on "place order" might pass through a gateway, an order service, inventory and payments, each on a different machine. Every service records a span for its piece of the work: what it did, when it started, how long it took and whether it failed. All the spans from one request share a trace id, so the backend can put them back together into one picture of the request. That picture answers questions that logs struggle with. Which service made this request slow? Where did the error start? A log line tells you about one event on one machine. A trace shows the full path of one request, with a timing for every hop and every step inside a hop.
The prompt has two halves, and the round can lean on either. Building the library is low-level design: a clean API, the classes behind it, thread safety and what runs on the request thread. On the backend side it's high-level design: ingest, storage, queries and scale. This lesson covers both, because the prompt asks for both and the interviewer picks which one to push on.
NutanixPremium lesson · System design round
The Nutanix design, worked end to end.
- The API and data modelSystem design
- The design, drawn out2 diagrams
- 6 deep divesWith the tradeoffs
$49 a year · all 107 companies · instant access
131 Nutanix interview reports · guide updated
Nutanix interview guideKnow what Nutanix asks before you walk in.
30 coding · 4 system design · 15 behavioral questions
Get their questions first.
InterviewLegend is independent and not affiliated with or endorsed by any company it covers.