Design a Payment Service
Last updated: April 5, 2026
Quick Overview
Design a low-latency payment system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Twitter/X
System Design
Software Engineer
Twitter/X
April 5, 2026Software Engineer
Onsite
System Design
Easy
35
10
944 solved
Design a low-latency payment system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
ML system design at Twitter/X goes beyond model selection. This Onsite question evaluates your ability to design end-to-end ML pipelines, from data collection to model serving, while considering production constraints like latency and reliability.
What the Interviewer Expects
- Map the business problem to a concrete ML objective
- Propose reasonable features and a baseline model
- Discuss basic model evaluation metrics
- Outline a simple serving architecture
Key Topics to Cover
Model serving and latency optimization
Online vs offline evaluation
Model selection and architecture
Data collection and labeling strategy
Feedback loops and model retraining
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 handle a 10x increase in prediction requests?
- How would you run A/B tests on different model versions?
- How would you debug a model that works well offline but poorly online?
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:
- Handle payment transactions securely and efficiently.
- Support various payment methods (credit card, PayPal, etc.).
- Provide real-time transaction status updat...
Capacity Estimation
- Assume an average transaction size of 250 bytes.
- For 10 million transactions per day, this results in approximately:
- 10,000,000 transactions/day * 250 bytes/transaction = 2.5 GB/day.
- With pe...
Submit Your Answer
Markdown supported