Design a large-scale Payment Platform
Last updated: November 4, 2025
Quick Overview
Design a geo-distributed payment system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Uber
November 4, 2025170
6
3,638 solved
Design a geo-distributed payment system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Uber asks this during the Technical Screen 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
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 schema migrations with zero downtime?
- How would you optimize costs as the system scales?
- How would you handle a 10x increase in traffic overnight?
- How would you implement rate limiting to protect the 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:
- Process payments for rides, food deliveries, and other services in real-time.
- Support multiple payment methods (credit cards, PayPal, etc.).
- Provide transact...
Capacity Estimation
Assuming Uber processes an average of 1,000 transactions per second (TPS) during peak hours:
- Daily Transactions: (1,000 , ext{TPS} imes 60 , ext{s} imes 60 , ext{min} imes 24 , ext{hour...
Submit Your Answer
