Build a scalable Feature Flag Pipeline

Last updated: June 7, 2026

Quick Overview

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

Salesforce
System Design
Software Engineer
Salesforce
June 7, 2026
Software Engineer
System Design Round
System Design
Medium

340

12

2,984 solved


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

Salesforce 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
  • 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
Requirements gathering and capacity estimation
Caching strategies (local, distributed, CDN)
High-level architecture and component design
Security and authentication
API design and rate limiting
Consistency models and replication
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
  • What would the deployment pipeline look like for this system?
  • What monitoring and alerting would you set up on day one?
  • 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 Codemia
Sample Answer
Requirements

Functional Requirements

  1. Feature Management: Enable the creation, updating, and deletion of feature flags by authorized users.
  2. User Targeting: Support targeting specific user segments...
Capacity Estimation

Capacity Estimation

Assuming Salesforce has approximately 1 million active users:

  • Requests per Second (QPS): If each user generates an average of 10 flag checks per minute, we have:
    • 1,00...

Submit Your Answer
Markdown supported

Related Questions