Design a large-scale Data Pipeline Platform
Last updated: April 1, 2026
Quick Overview
Design a real-time data pipeline system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
PayPal
April 1, 202610
15
4,477 solved
Design a real-time data pipeline system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
System design interviews at PayPal typically last 45-60 minutes. You are expected to drive the conversation, starting from requirements gathering through to a detailed architecture. The interviewer will evaluate your ability to handle ambiguity and make practical engineering decisions.
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
- What would the deployment pipeline look like for this system?
- How would you implement rate limiting to protect the system?
- What happens if one of your database nodes goes down?
- How would you migrate from a monolithic to a microservices architecture?
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
- Real-time Data Ingestion: The system should support the ingestion of millions of events per second from various sources (e.g., transactions, user activities).
- **D...
Capacity Estimation
Assuming PayPal processes 300 million transactions per day, which translates to approximately 3,500 transactions per second (TPS). If we consider each transaction generates 10 events (e.g., transactio...
Submit Your Answer
