System Design, Redis & Distributed Systems
8-10 Years (Tech Lead)
Hard
Production Scenario
How does Log Aggregation and Distributed Tracing work with OpenTelemetry, Jaeger, and ELK Stack?
Real-World Scenario / Incident Description
A user checkout request spans 6 microservices and 14 database queries. How do you trace where the latency occurred using a unified `trace_id`?
60 views
•
Updated 1 month ago
Distributed Context Propagation
- The edge API gateway generates a unique
trace_idandspan_id. - Passed downstream across all HTTP/gRPC headers via W3C Trace Context (
traceparent: 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01). - Each microservice logs the
trace_idand exports span metrics to OpenTelemetry collector / Jaeger for visual timeline waterfalls.
Related Concepts:
#Distributed Tracing
#OpenTelemetry
#Jaeger
#Observability
More System Design, Redis & Distributed Systems Interview Questions
How does the Redis Redlock Algorithm provide Fault-Tolerant Distributed Locking across independent Redis nodes?
Read →
Explain the 3 High-Scale Cache Failure Patterns: Cache Avalanche, Cache Breakdown (Dog-Piling), and Cache Penetration, with mitigations.
Read →
Compare Rate Limiting Algorithms: Token Bucket, Leaky Bucket, Fixed Window Counter, and Sliding Window Log/Counter.
Read →
How do you design a Real-Time Notification System delivering to 10M concurrent users with WebSockets and Redis Pub/Sub?
Read →
How do you design an Idempotent Payment Processing Architecture with the Saga Pattern across Microservices?
Read →