Transactional systems case
Design a hotel booking system
Use transactions, idempotency, and state machines to protect booking inventory
Start with date and inventory boundaries, then design multi-night transactions, payment holds, one inventory source across travel channels, cached reads, and concurrent release.
TransactionsConsistencyIdempotencyInventory holds
Case path
Work through the design decisions
- 01Part C: Hotel Booking — ClarifyFree account
- 02Part C: Hotel Booking — Scope and prioritiesFree account
- 03Part C: Hotel Booking — Architecture and oversell preventionFree account
- 04Part C: Hotel Booking — T1–T5 simulationFree account
- 05Part C: Hotel Booking — Bottlenecks, verification, and reusable patternsFree account