Design a large-scale A/B Testing Platform
Last updated: April 10, 2026
Quick Overview
Design a distributed a/b testing system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Mastercard
April 10, 20263
13
2,865 solved
Design a distributed a/b testing system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
System design interviews at Mastercard 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
- Systematically gather requirements and estimate capacity (QPS, storage, bandwidth)
- Design a scalable architecture with clear component responsibilities
- Make well-reasoned database and caching decisions with trade-off analysis
- Address consistency vs availability trade-offs specific to the use case
- Discuss partitioning strategy, replication, and data modeling
- Cover failure handling, monitoring, and alerting strategies
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 happens if one of your database nodes goes down?
- How would you optimize costs as the system scales?
- How would you handle a region-wide outage?
- What would the deployment pipeline look like for this 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
- Experiment Creation: Users must be able to create A/B tests specifying variants, metrics, and targeting parameters.
- Traffic Allocation: The system must suppor...
Capacity Estimation
Assuming Mastercard runs multiple A/B tests concurrently:
- User Base: Let's estimate around 100 million active users.
- Active Tests: Assuming an average of 10 active tests at any time, with ...
Submit Your Answer
