Design Payment Infrastructure for microservices
Last updated: August 15, 2025
Quick Overview
Design a scalable payment system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Airbnb
System Design
Software Engineer
Airbnb
August 15, 2025Software Engineer
Onsite
System Design
Medium
1
14
2,116 solved
Design a scalable payment system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
System design interviews at Airbnb typically last 45-60 minutes. You are expected to drive the conversation, starting from requirements gathering through to a detailed architecture. The interviewer will evaluate your ability to handle ambiguity and make practical engineering decisions.
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
High-level architecture and component design
Security and authentication
Database selection and data modeling
API design and rate limiting
Caching strategies (local, distributed, CDN)
Message queues and async processing
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
- What would the deployment pipeline look like for this system?
- How would you handle a 10x increase in traffic overnight?
- What monitoring and alerting would you set up on day one?
- 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
- User Payment Processing: Support credit card payments, debit payments, and digital wallets for booking accommodations.
- Refund Management: Enable users to requ...
Capacity Estimation
Back-of-Envelope Calculations
- User Base: Assume 10 million active users.
- Transactions per User: Estimate an average of 0.5 transactions per user per day, leading to 5 million transacti...
Submit Your Answer
Markdown supported