Why this matters
- Checked vs unchecked — detailed pointwise breakdown in the section below.
- Domain exceptions — detailed pointwise breakdown in the section below.
- Error codes — detailed pointwise breakdown in the section below.
- CampusOS payments — detailed pointwise breakdown in the section below.
- Production Java structure interviewers expect in backend LLD.
Dependency direction
Controller / FacadeHTTP or API entry
Serviceuse cases, orchestration
Domainentities, rules, invariants
Repositorypersistence port
Overview
Domain errors vs infrastructure failures — typed, not stringly. Study each section below in order — every list is interview-ready reference material.
Checked vs unchecked
Points to cover
- Definition — what Checked vs unchecked means in one clear sentence
- When to use — the force or smell that triggers this concept
- CampusOS example — where this appears in parking, booking, or library modules
- How to explain — pointwise bullets you can say aloud in an interview
- Common mistake — what weak candidates do instead
- Refactor move — one concrete change that improves the design
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 · 3 sections
- Domain exceptions
- Error codes
- CampusOS payments
Test yourself
Answer these before moving on — recall is what makes it stick.