Why this matters
- Users create events with start, end, attendees, and optional room
- Scope — what "Event model" covers inside Meeting Scheduler and what it does not
- Scope — what "Conflict check" covers inside Meeting Scheduler and what it does not
- Scope — what "Recurrence" covers inside Meeting Scheduler and what it does not
- Booking problems test inventory, overlap, and concurrent holds.
BookingService
Resourceroom, seat, table
TimeSlotstart, end, capacity
Reservationstatus, userId
CampusOS context
CampusOS is the fictional smart-campus platform used across this track. Treat this module as a real product slice:
Context
- Belongs to CampusOS — same naming and design vocabulary as parking, library, and booking modules
- Scope is one JVM — persistence is in-memory or behind a repository interface
- Goal is a class diagram + core Java that an interviewer can follow in 35–45 minutes
- Extension paragraph at the end links to System Design when scale exceeds one process
Requirements snapshot
Functional requirements
- Users create events with start, end, attendees, and optional room
- Detect conflicts for same attendee or same room
- Recurring events (daily, weekly) expand to instances
- Update or cancel single occurrence vs whole series
- Free-busy lookup for scheduling assistant
Non-functional requirements
- Single JVM, in-process design for this LLD article
- Core flows testable with in-memory repositories
- Extension points for new rules without editing central god classes
- Clear public API on facade/service layer
- CampusOS extension links to System Design when scale demands distribution
The rest of this guide is part of Pro
Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.
Still to come · 6 sections
- Overview
- Requirements
- Event model
- Conflict check
- Recurrence
- CampusOS extension
Test yourself
Answer these before moving on — recall is what makes it stick.