Commerce & Money: Hotel/Ticket Booking, E-commerce, Payment System & Digital Wallet
Five end-to-end case studies where a wrong answer costs real money: inventory that must never oversell, seats held under flash-sale load, carts that turn into orders, payments that must happen exactly once, and wallets that must balance to the paisa.
About 150 minutes · 15 exam questions · 9 interview questions · 2 code labs
What you will learn
- Why commerce designs are different: correctness is the product
- Hotel reservation (1/3): requirements, estimation, API and data model
- Hotel reservation (2/3): architecture and the double-booking problem
- Hotel reservation (3/3): scaling, caching and cross-service consistency
- Ticket booking (1/2): BookMyShow/Ticketmaster seat holds with TTL
- Ticket booking (2/2): the virtual waiting room for flash sales
- E-commerce (1/2): cart, checkout API and order data model
- E-commerce (2/2): inventory reservation and the checkout saga
- Payment system (1/3): requirements, estimation and the pay-in flow
- Payment system (2/3): the double-entry ledger
- Payment system (3/3): idempotency, retries, webhooks and reconciliation
- Digital wallet (1/2): 1M TPS, in-memory vs DB, and distributed transactions
- Digital wallet (2/2): event sourcing, CQRS and Raft-replicated state
- Wrap-up: trade-offs across the five designs
- Level bar: what mid, senior and staff answers include
- Deep-dive ladders: bad → good → great
Previous: Infrastructure Systems: Distributed Message Queue, Metrics Monitoring, Ad Click Aggregation, Job Scheduler & Logging Platform · Next: Storage Systems: Dropbox/Google Drive, Distributed Email & Distributed File System