Architect a low-latency Feature Flag Engine
Last updated: December 17, 2025
Quick Overview
Design a low-latency feature flag system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Datadog
System Design
Software Engineer
Datadog
December 17, 2025Software Engineer
System Design Round
System Design
Medium
0
6
4,063 solved
Design a low-latency feature flag system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Datadog asks this during the System Design Round to assess your understanding of the full ML lifecycle. They want to see how you translate a business problem into an ML objective, design the feature pipeline, and plan for model monitoring and retraining.
What the Interviewer Expects
- Define clear ML objectives with appropriate loss functions and metrics
- Design a comprehensive feature engineering pipeline
- Discuss model selection with trade-offs (complexity vs interpretability vs latency)
- Plan online and offline evaluation strategies including A/B testing
- Address serving infrastructure: batch vs real-time, latency requirements
- Consider data quality, labeling strategy, and feedback loops
Key Topics to Cover
Training pipeline and infrastructure
A/B testing and experimentation
Feature engineering and feature stores
Monitoring and model degradation detection
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 the cold start problem?
- How would you debug a model that works well offline but poorly online?
- How would you ensure fairness and reduce bias in the model?
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
- Feature Flag Creation and Management: Users can create, update, delete, and manage feature flags via a web interface and API.
- User Segmentation: Ability to ta...
Capacity Estimation
Back-of-Envelope Calculations
- User Base: Assume 10 million active users.
- Request Rate: If each user generates 10 requests per day, that’s 100 million requests per day, translating to ~...
Submit Your Answer
Markdown supported