How do correlation ids make a distributed trace useful across Spring and Kafka?
PICTURE THIS: A REST CALL
Simple meaning
The first hop generates a trace id, puts it on MDC logs, HTTP headers, and Kafka headers, and every service continues the same id.
WHY — Microservices instead of guessing?
Why interviewers care about Microservices:
question about Microservices.
trade-offs, and what you would actually do on a Backend project - not buzzwords.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1The first hop generates
a trace id, puts it on MDC logs, HTTP headers, and Kafka headers, and every service continues the same id.
- 2You can then jump
from a 500 in the gateway to the consumer that failed.
- 3Without header propagation, each
service has a pretty but isolated log.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
The first hop generates a trace id, puts it on MDC logs, HTTP headers, and Kafka headers, and every service continues the same id. You can then jump from a 500 in the gateway to the consumer that failed.