Design a Logging Service
Last updated: May 12, 2026
Quick Overview
Design a event-driven logging system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Waymo
May 12, 202637
13
1,468 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 Technical Screen at Waymo. 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. Waymo 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
- What happens if one of your database nodes goes down?
- How would you handle a region-wide outage?
- How would you implement rate limiting to protect the system?
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 Logging: Capture various events such as vehicle diagnostics, route updates, and user interactions in real-time.
- Search and Retrieval: Allow users to qu...
Capacity Estimation
- Assumptions:
- Average log size: 1 KB
- Estimated number of vehicles: 10,000
- Average logs per vehicle per second: 10
- Peak hours: 4 hours/day
- Total operating hours: 24 hours...
Submit Your Answer
