Build a fault-tolerant A/B Testing Pipeline
Last updated: January 18, 2026
Quick Overview
Design a fault-tolerant a/b testing system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Twitter/X
January 18, 20266
13
1,111 solved
Design a fault-tolerant a/b testing 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 handle schema migrations with zero downtime?
- How do you ensure data consistency across multiple services?
- 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:
- Ability to create, manage, and analyze A/B tests for various features of the Twitter/X platform.
- Support for multiple variations in each test (e.g., contro...
Capacity Estimation
- User Base: Assume Twitter/X has 300 million daily active users.
- A/B Tests: Assume an average of 10 concurrent A/B tests, each with 4 variations.
- Requests per Second:
- 300 mi...
Submit Your Answer
