How qkrgusrb0123a-ui/week10_workout works
Concert Ticketing is a mock ticket-reservation web app. Visitors browse performances and seat availability, enter the queue when booking access is limited, select a seat, complete a security challenge, and then retrieve or cancel a reservation. The Express API serves the frontend and routes concert, queue, and reservation requests; SQLite stores the catalog, seats, and reservation history. Queue admission and booking challenges are in-memory services. The excerpts show the main server wiring and booking flows; some frontend and reservation-page interactions are documented in the README but their source was not excerpted.
Main entry points: api.js Fetch API client · reservations.js Reservation routes · app.js Express app · queue.js Queue routes
Components 13
Web frontend
- Concert listing
public/js/index.js - Seat booking
public/js/concert.js - Queue status
public/js/waiting.js - Reservation lookup
public/js/reservation.js - Fetch API client
public/js/api.js
API server
- Express app
server/app.js - Concert routes
server/routes/concerts.js - Queue routes
server/routes/queue.js - Reservation routes
server/routes/reservations.js
Booking services
- Admission queue
server/services/queue.js - Security challenge
server/services/booking.js
Persistent data
- SQLite database
server/db.js
Other components
- Visitor
Connections 21
- Visitor → Concert listing: browses
README.md - Visitor → Seat booking: selects seats
README.md - Visitor → Queue status: waits in
README.md - Visitor → Reservation lookup: checks booking
README.md - Concert listing → Fetch API client: requests concerts
public/js/index.js - Seat booking → Fetch API client: requests booking
public/js/concert.js - Queue status → Fetch API client: polls queue
public/js/waiting.js - Reservation lookup → Fetch API client: uses booking API
README.md - Express app → Concert routes: mounts routes
server/app.js - Express app → Queue routes: mounts routes
server/app.js - Express app → Reservation routes: mounts routes
server/app.js - Express app → SQLite database: checks health
server/app.js - Fetch API client → Concert routes: calls API
public/js/api.js - Fetch API client → Queue routes: calls API
public/js/api.js - Fetch API client → Reservation routes: calls API
public/js/api.js - Concert routes → SQLite database: reads catalog
server/routes/concerts.js - Queue routes → SQLite database: checks concert
server/routes/queue.js - Queue routes → Admission queue: manages tickets
server/routes/queue.js - Reservation routes → SQLite database: books and cancels
server/routes/reservations.js - Reservation routes → Admission queue: validates admission
server/routes/reservations.js - Reservation routes → Security challenge: creates and verifies
server/routes/reservations.js