Clean Architecture Layers
ELI5 — The Vibe Check
Clean Architecture's layers go: Entities (business rules) -> Use Cases (app rules) -> Interface Adapters (controllers, presenters) -> Frameworks & Drivers (web, DB). Each layer only knows about the one inside it. It's the architecture that Uncle Bob won't stop talking about.
Real Talk
Robert C. Martin's layered architecture defining four concentric layers: Entities (enterprise business rules), Use Cases (application business rules), Interface Adapters (gateways, controllers, presenters), and Frameworks & Drivers (UI, database, external services). The dependency rule mandates that dependencies only point inward.
When You'll Hear This
"In Clean Architecture, use cases orchestrate entities but never know about the database." / "The dependency rule is everything — inner layers never import from outer layers."
Related Terms
Hexagonal Architecture
Hexagonal Architecture (aka Ports and Adapters) treats your app like a USB hub.
Onion Architecture
Onion architecture arranges code in concentric layers like an onion. The core (domain) has no dependencies. Each outer layer depends inward, never outward.
SOLID (SOLID)
SOLID is five rules for writing code that doesn't turn into a nightmare over time. Each letter stands for a different rule.
Use Case
A use case is a single thing a user can do with your system — 'Place Order', 'Register Account', 'Cancel Subscription.