Build a event-driven Logging Pipeline
Last updated: April 1, 2026
Quick Overview
Design a event-driven logging system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Datadog
April 1, 202626
8
1,976 solved
Design a event-driven logging system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
This is a common system design question asked during System Design Round at Datadog. The interviewer expects you to demonstrate your ability to design large-scale distributed systems, make well-reasoned trade-offs, and communicate your thought process clearly. Datadog values engineers who can think about scalability from day one.
What the Interviewer Expects
- Systematically gather requirements and estimate capacity (QPS, storage, bandwidth)
- Design a scalable architecture with clear component responsibilities
- Make well-reasoned database and caching decisions with trade-off analysis
- Address consistency vs availability trade-offs specific to the use case
- Discuss partitioning strategy, replication, and data modeling
- Cover failure handling, monitoring, and alerting strategies
Key Topics to Cover
How to Approach This
- Start by clarifying functional and non-functional requirements with the interviewer.
- Estimate the scale: QPS, storage, bandwidth. This drives your design decisions.
- Draw a high-level architecture first, then deep dive into 1-2 critical components.
- Discuss trade-offs explicitly (e.g., consistency vs availability, SQL vs NoSQL).
- Address failure scenarios, monitoring, and how the system handles 10x traffic spikes.
Possible Follow-up Questions
- How would you handle a region-wide outage?
- How do you ensure data consistency across multiple services?
- How would you optimize costs as the system scales?
Practice a Similar Problem on Codemia
Solve a related problem with our interactive workspace, get AI feedback, and view detailed solutions.
Solve on CodemiaSample Answer
Requirements
Functional Requirements:
- Event Ingestion: The system should ingest log events from various sources (servers, applications, services) in real-time.
- Event Processing: Process and enric...
Capacity Estimation
Back-of-Envelope Calculations:
Assuming the following:
- Event Size: Each log event averages 1 KB.
- Peak Load: Anticipate 100 million events per day (approximately 1,157 events per second...
Submit Your Answer
