Architect a low-latency Logging Engine
Last updated: December 31, 2025
Quick Overview
Design a low-latency logging system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Dropbox
December 31, 20252
12
2,134 solved
Design a low-latency logging system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
ML system design at Dropbox goes beyond model selection. This Onsite question evaluates your ability to design end-to-end ML pipelines, from data collection to model serving, while considering production constraints like latency and reliability.
What the Interviewer Expects
- Map the business problem to a concrete ML objective
- Propose reasonable features and a baseline model
- Discuss basic model evaluation metrics
- Outline a simple serving architecture
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 would you do if model performance degrades over time?
- What is your model retraining strategy?
- How would you handle the cold start problem?
- How would you ensure fairness and reduce bias in the model?
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 Clarification
Before diving into the architecture, clarify the scope with the interviewer. For low-latency Logging Engine, key functional requirements include: what...
Capacity Estimation
Estimate the scale to drive design decisions. Assume 100M DAU with an average of 10 actions per user per day = 1B requests/day ~ 12K QPS average, ~36K...
Submit Your Answer
