Skip to main content
PreparationZone Logo
PrepZone

Layered Architecture in Practice

Controller, service, domain, repository — who calls whom.

Pass checkpoint below

Why this matters

  • Layer responsibilities — detailed pointwise breakdown in the section below.
  • Dependency rule — detailed pointwise breakdown in the section below.
  • CampusOS booking service — detailed pointwise breakdown in the section below.
  • Thin controllers — 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
Dependencies point inward — domain never imports infrastructure.

Overview

Controller, service, domain, repository — who calls whom. Study each section below in order — every list is interview-ready reference material.

Layer responsibilities

Points to cover

  • Definition — what Layer responsibilities 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

  • Dependency rule
  • CampusOS booking service
  • Thin controllers

Test yourself

Answer these before moving on — recall is what makes it stick.