CSE Roadmap

Core tier · about 4 hours · 6 parts

Part 1 of 6 · 1 min read

Why this page comes fifth in Level 7

In this module you will

  • Turn a booking question into requirements about seats, shows, holds and payment.
  • Model seats as values and the seat map as the one place that decides who owns a seat.
  • Build a hold that expires, and a confirm step that checks the hold is still valid.
  • Make a multi-seat hold all-or-nothing, and prove that only one of 100 racing callers wins.
  • Plug in pricing rules without touching the booking code.

Booking questions test one thing above all: two people must never get the same seat. That is the check-then-act race of Level 5, module 3, in its most familiar costume. The page also adds a timed hold, which many designs forget. No book was supplied for this track, so the content is common practice, not from the books. The Java code was compiled and run before it was written here. Numbers marked "made up" only show the idea.