Build a geo-distributed Logging Pipeline
Last updated: August 26, 2025
Quick Overview
Design a geo-distributed logging system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Snowflake
August 26, 2025203
11
4,499 solved
Design a geo-distributed logging system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Snowflake asks this during the Onsite to assess your architectural thinking. They want to see how you decompose a complex problem, choose appropriate technologies, and reason about failure modes. Strong candidates proactively discuss monitoring, alerting, and operational concerns.
What the Interviewer Expects
- Clearly define functional and non-functional requirements
- Propose a reasonable high-level architecture with core components
- Choose appropriate data storage solutions with basic justification
- Discuss basic scaling strategies (horizontal scaling, caching)
- Identify potential bottlenecks and suggest simple solutions
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 10x increase in traffic overnight?
- What happens if one of your database nodes goes down?
- How would you migrate from a monolithic to a microservices architecture?
- How would you handle a region-wide outage?
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
- Log Ingestion: The system must accept log entries from various geo-distributed clients (e.g., applications, microservices) in real-time.
- Log Storage: Logs sho...
Capacity Estimation
To estimate capacity, let's assume the following:
- Each log entry is roughly 1 KB.
- We expect 1 million log entries per second during peak times.
- The system should support 5 regions worldwide.
##...