Build a geo-distributed Inventory Management Pipeline
Last updated: July 29, 2025
Quick Overview
Design a geo-distributed inventory management system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
PlanetScale
July 29, 202510
13
418 solved
Design a geo-distributed inventory management system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
System design interviews at PlanetScale 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
- 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 optimize costs as the system scales?
- What happens if one of your database nodes goes down?
- How would you migrate from a monolithic to a microservices architecture?
- How do you ensure data consistency across multiple services?
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
- Real-Time Inventory Tracking: The system must allow for real-time updates and queries of inventory levels across multiple geographic regions.
- User Management:...
Capacity Estimation
Assuming the following:
- Average of 1 million requests per day.
- Each request might involve fetching the inventory data, which can be around 1-2 KB in size.
- Peak traffic can spike to 10 times the ...
Submit Your Answer
