Why does the checkout service make the Astronomy Shop a good showcase for distributed tracing?

Because checkout is an orchestrator: one "place order" click fans out from checkout into payment, shipping, email and currency, producing a request that spans many services.

* One click, one orchestrator, five downstream calls: only a trace follows the whole order. *

The typical flow is Browser → Frontend → Checkout, and from there checkout calls Cart, Payment, Shipping and Email (plus Currency for the prices). None of these downstream services knows about the others; only checkout sees the whole order.

That makes it the textbook case for tracing. If an order takes four seconds, the frontend only sees "checkout was slow". Checkout's own logs say it waited a long time. The real question, which of the four downstream calls ate the time, is answered only by a trace that follows the single request through every hop. Each station along the way emits its own telemetry, and the trace ID ties it into one picture.

The same pattern exists in every real system with an orchestrating service (order processing, booking, onboarding), so learning to read this one trace transfers directly.