Build a scalable A/B Testing Pipeline

Last updated: November 23, 2025

Quick Overview

Design a scalable a/b testing system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.

Supabase
System Design
Software Engineer
Supabase
November 23, 2025
Software Engineer
System Design Round
System Design
Easy

63

13

2,784 solved


Design a scalable a/b testing system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.

Supabase asks this during the System Design Round 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
Security and authentication
Caching strategies (local, distributed, CDN)
Monitoring, logging, and alerting
High-level architecture and component design
Partitioning and sharding strategies
Failure handling and fault tolerance
How to Approach This
  1. Start by clarifying functional and non-functional requirements with the interviewer.
  2. Estimate the scale: QPS, storage, bandwidth. This drives your design decisions.
  3. Draw a high-level architecture first, then deep dive into 1-2 critical components.
  4. Discuss trade-offs explicitly (e.g., consistency vs availability, SQL vs NoSQL).
  5. 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?
  • How would you handle schema migrations with zero downtime?
  • How would you migrate from a monolithic to a microservices architecture?
  • What happens if one of your database nodes goes down?
Practice a Similar Problem on Codemia

Solve a related problem with our interactive workspace, get AI feedback, and view detailed solutions.

Solve on Codemia
Sample Answer
Requirements

Functional Requirements

  1. User Segmentation: The ability to segment users based on various criteria (e.g., demographics, behavior).
  2. Experiment Creation: Users can create, update, and d...
Capacity Estimation

Assuming Supabase handles 10 million active users and each user is part of an average of 5 A/B tests, we can estimate the following:

  • Total A/B Tests: 10 million users * 5 tests = 50 million A/B...

Submit Your Answer
Markdown supported

Related Questions