Why this matters
- Log at levels: TRACE, DEBUG, INFO, WARN, ERROR
- Scope — what "Level hierarchy" covers inside Logging Framework and what it does not
- Scope — what "Appenders" covers inside Logging Framework and what it does not
- Scope — what "Async queue" covers inside Logging Framework and what it does not
- In-memory systems test data structures + thread safety together.
Request
Auth
Validate
Handler
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
- Log at levels: TRACE, DEBUG, INFO, WARN, ERROR
- Multiple appenders: console, file, remote — per logger config
- Formatters control message layout (JSON, plain text)
- Async appender uses queue so caller thread is not blocked
- Child loggers inherit parent level unless overridden
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
- Level hierarchy
- Appenders
- Async queue
- CampusOS extension
Test yourself
Answer these before moving on — recall is what makes it stick.