Correlation IDs in Microservices - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a Correlation ID in microservices?

A Correlation ID is a unique identifier attached to a request that travels through multiple microservices. It helps track and trace the request across different services for debugging and monitoring.

beginner

Why are Correlation IDs important in distributed systems?

They allow developers to follow a request's path through many services, making it easier to find where errors or delays happen. This improves troubleshooting and system observability.

intermediate

How is a Correlation ID typically passed between microservices?

It is usually passed as a header in HTTP requests or as metadata in messaging systems, ensuring every service handling the request can log and forward the same ID.

intermediate

What happens if a Correlation ID is missing in a request?

The first service usually generates a new Correlation ID to start tracking. Without it, tracing the request end-to-end becomes difficult or impossible.

advanced

Name one best practice when implementing Correlation IDs.

Always generate the Correlation ID at the edge of the system (like API gateway) and ensure it is included in all logs and passed to downstream services.

What is the main purpose of a Correlation ID in microservices?

A To uniquely identify and trace a request across multiple services

B To encrypt data between services

C To balance load between servers

D To store user credentials securely

Correlation IDs help track requests across services, not for encryption, load balancing, or storing credentials.

Where is a Correlation ID usually stored when passing between services?

A In the user's browser cookies

B In HTTP headers or message metadata

C In the service's environment variables

D In the database only

Correlation IDs travel with requests, so they are passed in headers or message metadata, not stored only in databases or environment variables.

If a request arrives without a Correlation ID, what should happen?

A The first service generates a new Correlation ID

B The request is rejected immediately

C The request is processed without tracking

D The Correlation ID is fetched from a cache

To maintain traceability, the first service creates a new Correlation ID if missing.

Which of the following is NOT a benefit of using Correlation IDs?

A Easier performance analysis

B Better request traceability

C Improved debugging and monitoring

D Automatic data encryption

Correlation IDs do not provide encryption; they help with tracing and monitoring.

Best practice for Correlation IDs includes:

A Not logging the ID to avoid clutter

B Changing the ID at every service

C Generating the ID at the system edge and passing it downstream

D Using random IDs for each service call

The ID should be generated once and passed along unchanged to maintain traceability.

Explain what a Correlation ID is and how it helps in microservices.

Think about how you follow a package delivery across multiple stops.

Describe the best practices for implementing Correlation IDs in a distributed system.

Consider how a tracking number stays the same from sender to receiver.