Phase 1 — Clarify & Scope
Interviewer: Design an e-commerce platform like Amazon. What do you want to clarify?
Candidate: This is a massive domain — I want to understand the scope:
- Are we designing the full platform or a specific subsystem? I'd suggest focusing on the core: product catalog, shopping cart, order placement, and inventory management.
- What's the scale — users, orders per day, catalog size?
- First-party inventory (Amazon owns the stock) or marketplace (third-party sellers)?
- Are we including fulfillment/shipping, or just the order system?
- How critical is consistency for inventory — can we oversell (like airline overbooking), or must we be exact?
Interviewer: Full platform. Focus on product catalog + search, shopping cart, order placement, and inventory management. 300 million active users, 10 million orders per day, 500 million product SKUs. Both first-party and third-party sellers. Include inventory management. No overselling — don't show "Add to Cart" if out of stock.
Candidate: Let me size this:
Cart sessions: 300M users × 30% with active carts = 90M active cart sessions.
In the full tutorial
- Phase 2 — High-Level Architecture
- Phase 3 — Deep Dive & Evolution
- Phase 4 — Robustness & Operations