7a:T49e,Before diving into specific requirements, we need to understand what makes e-commerce uniquely challenging from a system design perspective. E-commerce platforms sit at the intersection of multiple complex domains: **High-Read, High-Write Workloads:** Unlike social media (read-heavy) or banking (write-heavy), e-commerce demands excellence in both. Product browsing generates massive read traffic, while cart operations, orders, and inventory updates create significant write pressure. **Real-Time Consistency Requirements:** When a customer adds the last item in stock to their cart, the system must ensure they actually get it—not someone else who clicked a millisecond later. Yet strict consistency at global scale is architecturally expensive. **Financial Transactions:** Unlike content platforms where occasional errors are tolerable, e-commerce involves real money. A bug that charges a customer twice or ships incorrect inventory creates legal liability and destroys trust. **Variable Traffic Patterns:** E-commerce traffic is notoriously spiky. Black Friday can bring 20x normal traffic within minutes. The system must scale elastically while maintaining performance.7b:T511,// Product Catalog Service API interface ProductCatalogAPI { // Product retrieval getProduct(productId: string): Promise; getProductVariants(productId: string): Promise; // Search and discovery searchProducts(query: SearchQuery): Promise; getCategory(categoryId: string): Promise; getCategoryProducts(categoryId: string, pagination: Pagination): Promise; // Pricing (real-time, may include dynamic pricing) getPrice(productId: string, variantId?: string, userId?: string): Promise; // Availability (delegates to inventory service internally) getAvailability(productId: string, variantId: string, location: Location): Promise; } interface SearchQuery { query: string; filters: Filter[]; // Brand, price range, ratings, etc. sortBy: SortOption; // Relevance, price, rating, newest pagination: Pagination; userId?: string; // For personalized ranking } interface SearchResults { products: ProductSummary[]; facets: Facet[]; // Available filter options with counts totalCount: number; pagination: PaginationResult; searchMetadata: { queryInterpretation: string; spellCorrection?: string; suggestedQueries: string[]; }; }7c:T4fb,// Shopping Cart Service API interface CartAPI { // Cart operations getCart(sessionId: string, userId?: string): Promise; addToCart(request: AddToCartRequest): Promise; updateQuantity(request: UpdateQuantityRequest): Promise; removeFromCart(request: RemoveFromCartRequest): Promise; // Session management mergeGuestCart(guestSessionId: string, userId: string): Promise; // Saved items saveForLater(cartItemId: string): Promise; moveToCart(savedItemId: string): Promise; // Validation validateCart(sessionId: string): Promise; } interface AddToCartRequest { sessionId: string; userId?: string; productId: string; variantId: string; quantity: number; metadata?: Record; // Gift wrapping, customization } interface CartUpdateResult { cart: Cart; success: boolean; warnings: CartWarning[]; // Low stock, price changed, etc. errors: CartError[]; // Out of stock, invalid variant, etc. } interface Cart { id: string; items: CartItem[]; subtotal: Money; estimatedShipping: Money; estimatedTax: Money; total: Money; appliedPromotions: Promotion[]; lastUpdated: Timestamp; }7d:T53f,// Checkout Service API interface CheckoutAPI { // Checkout flow initiateCheckout(cartId: string): Promise; setShippingAddress(sessionId: string, address: Address): Promise; setShippingOption(sessionId: string, optionId: string): Promise; applyPromoCode(sessionId: string, code: string): Promise; // Payment setPaymentMethod(sessionId: string, paymentMethod: PaymentMethod): Promise; submitOrder(sessionId: string): Promise; // Order retrieval getOrder(orderId: string, userId: string): Promise; getOrderHistory(userId: string, pagination: Pagination): Promise; } interface CheckoutSession { id: string; cart: Cart; shippingAddress?: Address; billingAddress?: Address; shippingOptions: ShippingOption[]; selectedShipping?: ShippingOption; paymentMethod?: PaymentMethodSummary; // Calculated totals subtotal: Money; shippingCost: Money; tax: Money; discount: Money; total: Money; // Validation state readyForPayment: boolean; validationErrors: ValidationError[]; expiresAt: Timestamp; } interface OrderResult { success: boolean; orderId?: string; confirmationNumber?: string; estimatedDelivery?: DateRange; error?: PaymentError | InventoryError; }72:{"json":{"id":"seed_4aa2a8348fad3d3b7910797d9d317daf","slug":"amazon-e-commerce","category":"System Design HLD","topic":"Amazon E-Commerce","title":"Designing Amazon: E-Commerce at Massive Scale","description":"Master the architecture of large-scale e-commerce platforms. Learn to design product catalogs handling billions of items, shopping carts with session persistence, inventory systems with real-time stock management, order processing pipelines, and recommendation engines—all operating at Amazon-scale with millions of concurrent users.","difficulty":"ADVANCED","estimatedMinutes":120,"pages":[{"id":"seed_591b1926ad29b4e0bb73f7a383f112ef","title":"Requirements: Catalog, Cart, and Checkout","order":0,"content":[{"id":"opening-hook","title":"The E-Commerce Engineering Challenge","content":[{"data":{"content":"Amazon processes over **4,000 orders per minute** globally. Its product catalog contains more than **350 million unique items**. During peak events like Prime Day, the platform handles **hundreds of millions of customer visits** in a single day, with shopping carts being created, modified, and abandoned at staggering rates. Every second of latency in checkout directly translates to **millions of dollars in lost revenue**.\n\nDesigning an e-commerce system at this scale isn't just about making products appear on a screen—it's about orchestrating a symphony of distributed systems that must work in perfect harmony: catalog services, inventory management, shopping cart persistence, payment processing, order fulfillment, and real-time recommendations.\n\nThis module will take you through the complete architecture of a system like Amazon, starting with what every great system design begins with: **understanding the requirements**."},"type":"text"},{"data":{"icon":"Target","title":"What You Will Learn","content":"By the end of this page, you will have a comprehensive understanding of the requirements—both functional and non-functional—for building an e-commerce platform at massive scale. You'll learn to think like a Principal Engineer scoping a system that must handle billions of operations daily while maintaining sub-second response times.","variant":"info"},"type":"callout"}]},{"id":"problem-space","title":"Understanding the E-Commerce Problem Space","content":[{"data":{"content":"$7a"},"type":"text"},{"data":{"items":["**Stateful User Sessions** — Shopping carts represent stateful sessions that must persist across devices, browsers, and even weeks of inactivity","**Inventory as a Shared Resource** — Unlike user-specific data, inventory is a global shared resource that creates contention and consistency challenges","**Payment Processing** — Integration with external payment gateways adds latency, failure modes, and security requirements not present in other systems","**Logistics Integration** — Orders flow into warehouse management, shipping carriers, and delivery tracking—each with their own systems and protocols","**Regulatory Compliance** — Tax calculation varies by jurisdiction, product returns have legal requirements, and data privacy laws apply globally"],"title":{"icon":"AlertTriangle","text":"Why E-Commerce is Architecturally Unique","type":"icon","color":"accent","variant":"outline-circle"},"variant":"glass"},"type":"list"}],"titleType":"number","titleNumber":1},{"id":"user-journeys","title":"Core User Journeys","content":[{"data":{"content":"Understanding user journeys is essential for requirements gathering. Each journey maps to specific system capabilities that must be designed and optimized. Let's trace through the complete customer experience:"},"type":"text"},{"data":{"type":"ordered","items":["Customer arrives at homepage and sees personalized recommendations","Customer enters search query (e.g., 'wireless headphones under $100')","Search returns relevant products with filtering options (brand, price, ratings, Prime eligibility)","Customer browses category pages, applies filters, sorts by relevance/price/ratings","Customer views product detail page with images, descriptions, reviews, variants","Customer sees 'Frequently Bought Together' and 'Customers Also Viewed' suggestions"],"title":{"icon":"User","text":"Journey 1: Product Discovery","type":"icon","color":"primary","variant":"outline-circle"},"variant":"accent"},"type":"list"},{"data":{"type":"ordered","items":["Customer clicks 'Add to Cart' on product page","System validates inventory availability in real-time","Mini-cart updates showing item count and total","Customer navigates to cart page to review selections","Customer modifies quantities, removes items, saves for later","Cart persists across devices (customer can start on mobile, finish on desktop)","System shows shipping estimates based on delivery location"],"title":{"icon":"ShoppingCart","text":"Journey 2: Cart Operations","type":"icon","color":"primary","variant":"outline-circle"},"variant":"accent"},"type":"list"},{"data":{"type":"ordered","items":["Customer clicks 'Proceed to Checkout'","System verifies user authentication (or prompts guest checkout)","Customer confirms/enters shipping address","Customer selects shipping speed (standard, expedited, Prime)","System calculates taxes based on shipping destination and product types","Customer selects payment method or enters new payment details","Customer applies promo codes or gift cards","System validates and reserves inventory before payment","Payment is processed (authorization, capture)","Order confirmation generated with estimated delivery date"],"title":{"icon":"CreditCard","text":"Journey 3: Checkout and Payment","type":"icon","color":"primary","variant":"outline-circle"},"variant":"accent"},"type":"list"},{"data":{"icon":"Lightbulb","title":"The Conversion Funnel","content":"At each step of the journey, some percentage of customers drop off. This is the 'conversion funnel.' System design directly impacts conversion—every 100ms of checkout latency can reduce conversion by 1%. Understanding these journeys isn't just academic; it's directly tied to revenue.","variant":"tip"},"type":"callout"}],"titleType":"number","titleNumber":2},{"id":"functional-requirements","title":"Functional Requirements","content":[{"data":{"content":"Functional requirements describe **what the system must do**. For an e-commerce platform, we can organize these into three major subsystems: Product Catalog, Shopping Cart, and Checkout/Order Processing."},"type":"text"},{"data":{"rows":[["CAT-001","Display product details including title, description, images, price, variants","P0","Medium"],["CAT-002","Support product search with full-text search and filters","P0","High"],["CAT-003","Organize products into hierarchical categories and subcategories","P0","Medium"],["CAT-004","Support product variants (size, color, configuration)","P0","High"],["CAT-005","Display product availability and estimated delivery date","P0","High"],["CAT-006","Show customer reviews and aggregate ratings","P1","Medium"],["CAT-007","Support multi-language product content","P1","Medium"],["CAT-008","Enable seller product listings with approval workflow","P1","High"],["CAT-009","Display dynamic pricing (sales, bulk discounts)","P0","High"],["CAT-010","Show related products and recommendations","P1","High"]],"caption":"Product Catalog Functional Requirements","headers":["Requirement ID","Requirement","Priority","Complexity"]},"type":"table"},{"data":{"rows":[["CART-001","Add items to cart with selected variants and quantity","P0","Medium"],["CART-002","Update item quantities in cart","P0","Low"],["CART-003","Remove items from cart","P0","Low"],["CART-004","Display cart total with itemized breakdown","P0","Medium"],["CART-005","Persist cart across sessions and devices for authenticated users","P0","High"],["CART-006","Merge guest cart with authenticated user cart on login","P1","High"],["CART-007","Save items for later without removing from consideration","P1","Medium"],["CART-008","Display real-time inventory warnings for low-stock items","P0","High"],["CART-009","Apply promotional codes and validate discount eligibility","P0","High"],["CART-010","Show estimated shipping cost based on default/selected address","P1","Medium"]],"caption":"Shopping Cart Functional Requirements","headers":["Requirement ID","Requirement","Priority","Complexity"]},"type":"table"},{"data":{"rows":[["CHK-001","Capture and validate shipping address","P0","Medium"],["CHK-002","Calculate shipping costs based on items, destination, and speed","P0","High"],["CHK-003","Calculate taxes based on destination jurisdiction","P0","High"],["CHK-004","Process payments through multiple payment methods","P0","High"],["CHK-005","Validate and reserve inventory during checkout","P0","Critical"],["CHK-006","Generate order confirmation with unique order ID","P0","Medium"],["CHK-007","Send order confirmation via email/SMS","P0","Low"],["CHK-008","Support guest checkout without requiring account creation","P1","Medium"],["CHK-009","Handle payment failures gracefully with retry options","P0","High"],["CHK-010","Support multiple shipping addresses per order (split shipments)","P2","High"]],"caption":"Checkout and Order Processing Functional Requirements","headers":["Requirement ID","Requirement","Priority","Complexity"]},"type":"table"},{"data":{"icon":"Info","title":"Priority Definitions","content":"**P0**: Must have for launch, no exceptions. **P1**: Highly important, should be in launch if possible. **P2**: Desirable, can be phased in post-launch. In interviews, always clarify priorities with your interviewer—this demonstrates product sense.","variant":"note"},"type":"callout"}],"titleType":"number","titleNumber":3},{"id":"non-functional-requirements","title":"Non-Functional Requirements","content":[{"data":{"content":"Non-functional requirements (NFRs) describe **how the system must perform**. For Amazon-scale e-commerce, these are not nice-to-haves—they're fundamental constraints that shape every architectural decision."},"type":"text"},{"data":{"items":["**Product Page Load**: p99 latency < 200ms (including personalized recommendations)","**Search Results**: p99 latency < 300ms for complex queries across 350M+ products","**Add to Cart**: p99 latency < 100ms with real-time inventory validation","**Checkout Page Load**: p99 latency < 200ms (critical path for conversion)","**Payment Processing**: p99 latency < 2 seconds (includes external gateway roundtrip)","**Order Confirmation**: Generated within 5 seconds of successful payment"],"title":{"icon":"Zap","text":"Performance Requirements","type":"icon","color":"primary","variant":"outline-circle"},"variant":"accent"},"type":"list"},{"data":{"items":["**Catalog Size**: Support 500M+ products with 10K+ attributes each","**Active Users**: Handle 500M+ daily active users across all regions","**Concurrent Sessions**: Support 10M+ concurrent shopping sessions","**Orders Per Second**: Process 10,000+ orders per second during peak","**Search Queries**: Handle 100,000+ search queries per second","**Traffic Spikes**: Elastically scale to 20x baseline within 15 minutes"],"title":{"icon":"TrendingUp","text":"Scalability Requirements","type":"icon","color":"primary","variant":"outline-circle"},"variant":"accent"},"type":"list"},{"data":{"items":["**Catalog Service**: 99.99% availability (52 minutes downtime/year maximum)","**Cart Service**: 99.99% availability with zero cart data loss","**Checkout Service**: 99.999% availability (5 minutes downtime/year—payment-critical)","**Data Durability**: Zero tolerance for order data loss (11 nines durability)","**Disaster Recovery**: RTO < 15 minutes, RPO < 1 minute for all critical services","**Graceful Degradation**: Non-critical features (recommendations) fail without impacting core flow"],"title":{"icon":"Shield","text":"Availability and Reliability Requirements","type":"icon","color":"primary","variant":"outline-circle"},"variant":"accent"},"type":"list"},{"data":{"left":[{"data":{"items":["PCI-DSS Level 1 compliance for payment handling","End-to-end encryption for sensitive data in transit","Encryption at rest for all customer PII and payment tokens","Multi-factor authentication for account access","Rate limiting and fraud detection on all endpoints","SOC 2 Type II compliance for enterprise customers"],"title":{"icon":"Lock","text":"Security Requirements","type":"icon","color":"primary","variant":"outline-circle"},"variant":"glass"},"type":"list"}],"right":[{"data":{"items":["Multi-region deployment for latency and compliance","Support for multiple currencies with real-time conversion","GDPR compliance for European customers","Data residency requirements for specific regions","Localized payment methods (Alipay, UPI, SEPA, etc.)","Multi-language catalog and checkout support"],"title":{"icon":"Globe","text":"Global Requirements","type":"icon","color":"primary","variant":"outline-circle"},"variant":"glass"},"type":"list"}]},"type":"two-column"}],"titleType":"number","titleNumber":4},{"id":"scale-analysis","title":"Back-of-Envelope Scale Analysis","content":[{"data":{"content":"Before designing any system, we must understand its scale. Let's work through the numbers for an Amazon-scale e-commerce platform. These calculations inform capacity planning and help identify bottlenecks before they occur."},"type":"text"},{"data":{"code":"=== TRAFFIC ESTIMATION ===\n\nDaily Active Users (DAU): 500 million\nAverage Sessions per User per Day: 1.5\nPage Views per Session: 8\n\nTotal Daily Page Views: 500M × 1.5 × 8 = 6 billion page views/day\nQueries Per Second (QPS): 6B / 86,400 = ~70,000 QPS (average)\nPeak QPS: 5× average = ~350,000 QPS\n\n=== CART OPERATIONS ===\n\nUsers who add to cart: 30% of sessions\nItems added per cart session: 3.5 (average)\nCart add operations per day: 500M × 1.5 × 0.30 × 3.5 = ~790 million\n\nCart QPS: 790M / 86,400 = ~9,100 QPS (average)\nPeak Cart QPS: 5× average = ~45,000 QPS\n\n=== ORDER VOLUME ===\n\nConversion Rate: 2.5% of sessions result in order\nOrders per Day: 500M × 1.5 × 0.025 = ~18.75 million orders/day\nOrders Per Second: 18.75M / 86,400 = ~217 orders/second (average)\nPeak Orders Per Second: 10× average during events = ~2,200 OPS","title":"Traffic Estimation","language":"plaintext"},"type":"code"},{"data":{"code":"=== CATALOG STORAGE ===\n\nTotal Products: 350 million\nAverage Product Data Size: 50 KB (text, attributes, metadata)\nTotal Catalog Storage: 350M × 50 KB = 17.5 TB\n\nProduct Images per Product: 8 (average)\nAverage Image Size: 500 KB (optimized)\nTotal Image Storage: 350M × 8 × 500 KB = 1.4 PB\n\n=== CART STORAGE ===\n\nActive Carts (30-day active): 200 million\nAverage Cart Size: 2 KB (item references, quantities)\nActive Cart Storage: 200M × 2 KB = 400 GB\n\nCart History (1 year): 2 billion carts\nTotal Cart Storage: 2B × 2 KB = 4 TB\n\n=== ORDER STORAGE ===\n\nOrders per Year: 18.75M × 365 = 6.84 billion\nAverage Order Record Size: 10 KB (items, addresses, payment refs)\nAnnual Order Storage: 6.84B × 10 KB = 68.4 TB\nOrder History (5 years): 342 TB\n\n=== INVENTORY DATA ===\n\nInventory Records: 350M products × 10 regional warehouses = 3.5B\nRecord Size: 100 bytes (product ID, warehouse, quantity, reserved)\nTotal Inventory Data: 3.5B × 100 bytes = 350 GB (small but HOT)","title":"Storage Estimation","language":"plaintext"},"type":"code"},{"data":{"icon":"AlertCircle","title":"The Hot Path Problem","content":"Notice that inventory data is relatively small (350 GB) but represents the hottest data in the system—every cart operation, every checkout, every page view showing availability must read and potentially update this data. This is a classic scenario where data size doesn't correlate with access complexity.","variant":"warning"},"type":"callout"}],"titleType":"number","titleNumber":5},{"id":"system-constraints","title":"System Constraints and Trade-offs","content":[{"data":{"content":"Every large-scale system operates under constraints that shape its architecture. Understanding these constraints helps us make informed trade-offs rather than chasing impossible ideals."},"type":"text"},{"data":{"items":["**Catalog Data**: Eventual consistency is acceptable (seconds of delay for price updates tolerable)","**Inventory Data**: Must be strongly consistent for checkout, can be eventually consistent for display","**Cart Data**: Session-consistent (a user must see their own cart accurately, but cross-user consistency irrelevant)","**Order Data**: Strongly consistent and durable—no acceptable loss or inconsistency","**Payment Data**: ACID compliance required—financial transactions cannot be approximate"],"title":{"icon":"Database","text":"Data Consistency Constraints","type":"icon","color":"accent","variant":"outline-circle"},"variant":"glass"},"type":"list"},{"data":{"left":[{"data":{"items":["**Search**: Sacrifice consistency for speed—show slightly stale results","**Product Pages**: Cache aggressively—eventual consistency","**Cart Updates**: Optimize for responsiveness with async persistence","**Checkout**: No shortcuts—strong consistency required"],"title":{"icon":"Clock","text":"Latency vs Consistency Trade-offs","type":"icon","color":"primary","variant":"outline-circle"},"variant":"accent"},"type":"list"}],"right":[{"data":{"items":["**Hot Data in Memory**: Inventory, active carts, popular products","**Warm Data on SSD**: Full catalog, recent orders","**Cold Data on HDD/Archive**: Order history, analytics data","**Edge Caching**: Static assets, search suggestions"],"title":{"icon":"HardDrive","text":"Cost vs Performance Trade-offs","type":"icon","color":"primary","variant":"outline-circle"},"variant":"accent"},"type":"list"}]},"type":"two-column"},{"data":{"content":"**The CAP Theorem in E-Commerce Context:**\n\nFor a global e-commerce platform, we must choose carefully:\n\n1. **Catalog Service**: AP (Available + Partition Tolerant). During network partitions, we prefer showing potentially stale catalog data rather than failing requests. A customer seeing a slightly outdated price is better than seeing an error page.\n\n2. **Inventory Service**: CP (Consistent + Partition Tolerant) for checkout operations. We cannot risk overselling. During partitions, we may reject checkout operations rather than risk selling items we don't have.\n\n3. **Order Service**: CP with strong durability. Orders must never be lost or duplicated. We use synchronous replication and accept higher latency to guarantee consistency.\n\n4. **Cart Service**: AP with session consistency. We prefer cart availability over cross-device instant sync. Users can tolerate a few seconds of delay in cart syncing across devices."},"type":"text"}],"titleType":"number","titleNumber":6},{"id":"api-contracts","title":"Core API Contracts","content":[{"data":{"content":"Defining clear API contracts early helps align teams and clarifies system boundaries. Here are the critical API operations for our three core subsystems:"},"type":"text"},{"data":{"code":"$7b","title":"Product Catalog API","language":"typescript"},"type":"code"},{"data":{"code":"$7c","title":"Shopping Cart API","language":"typescript"},"type":"code"},{"data":{"code":"$7d","title":"Checkout API","language":"typescript"},"type":"code"}],"titleType":"number","titleNumber":7},{"id":"summary","title":"Requirements Summary","content":[{"data":{"content":"We've established a comprehensive requirements foundation for building an Amazon-scale e-commerce platform. Let's consolidate the key takeaways:"},"type":"text"},{"data":{"type":"ordered","items":["**E-commerce is uniquely demanding** — High-read, high-write, financial transactions, real-time inventory, and massive scale create a perfect storm of complexity","**Three core subsystems** — Product Catalog, Shopping Cart, and Checkout form the critical path; each has distinct consistency and latency requirements","**Scale is staggering** — Billions of page views, hundreds of millions of carts, tens of millions of orders daily require distributed systems expertise","**Consistency varies by subsystem** — Catalog can be eventual, orders must be strong, inventory needs both depending on context","**Latency directly impacts revenue** — Every 100ms in checkout latency can cost millions in lost conversions","**The inventory 'hot path'** — Small data that's accessed constantly represents the core bottleneck challenge"],"title":{"icon":"CheckCircle","text":"Key Requirements Insights","type":"icon","color":"primary","variant":"outline-circle"},"variant":"accent"},"type":"list"},{"data":{"content":"**What's Next:**\n\nWith requirements clearly defined, we'll dive into the first major subsystem: the Product Catalog. You'll learn how to design a system that can store, search, and serve 350+ million products with sub-200ms latency, support complex filtering and full-text search, and handle continuous updates from millions of sellers."},"type":"text"},{"data":{"icon":"CheckCircle","title":"Page Complete","content":"You now have a Principal Engineer's perspective on e-commerce system requirements. These requirements will guide every architectural decision in the pages ahead—from database selection to caching strategies to consistency models. Every trade-off we make will trace back to satisfying these requirements.","variant":"success"},"type":"callout"}],"titleType":"number","titleNumber":8}],"isLocked":false},{"id":"seed_014e57f8837bbd4dd765c9df8c47aea5","title":"Product Catalog at Scale","order":1,"content":null,"isLocked":true},{"id":"seed_80a65b5ce437671c200160a57ecaef4a","title":"Shopping Cart Design","order":2,"content":null,"isLocked":true},{"id":"seed_73d2759c4cb9e6ab8ed650f1fe67a2fc","title":"Inventory Management","order":3,"content":null,"isLocked":true},{"id":"seed_dd45c868e5ecff1a16cd62f2bcd3651e","title":"Order Processing","order":4,"content":null,"isLocked":true},{"id":"seed_9d48fac001c5fe722901f9fe836b75a1","title":"Recommendation Engine","order":5,"content":null,"isLocked":true}]}}