Design a Data Pipeline for Twitter/X
Last updated: February 3, 2026
Quick Overview
Design a multi-tenant data pipeline system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Twitter/X
February 3, 202643
3
4,936 solved
Design a multi-tenant data pipeline 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 Twitter/X. 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. Twitter/X values engineers who can think about scalability from day one.
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 migrate from a monolithic to a microservices architecture?
- What monitoring and alerting would you set up on day one?
- 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:
- Support multi-tenancy to handle data from different user accounts without interference.
- Enable data ingestion from various sources (tweets, retweets, likes, etc....
Capacity Estimation
- Estimating Scale:
- Assume Twitter/X has 450 million daily active users.
- Each user generates an average of 10 interactions (tweets, retweets, likes) per day.
- Total interactions per day...
Submit Your Answer
