Clean Architecture is a software design philosophy popularised by Robert C. Martin (Uncle Bob) that aims to create systems that are easy to understand, maintain, test, and extend over time.
Its central objective is the strict separation of concerns, ensuring that the application's business logic and rules remain completely independent from external details such as web frameworks, databases, or user interfaces.
1. The Core Principle: The Dependency Rule
The governing principle behind Clean Architecture is the Dependency RuleRegla de DependenciaPrincipio central de la Arquitectura Limpia que establece que las dependencias del código fuente solo pueden apuntar hacia adentro, es decir, hacia las capas que contienen la lógica de negocio y las reglas empresariales (Entidades y Casos de Uso). Ningún componente o clase de un círculo interno puede conocer, importar o hacer referencia directa a elementos ubicados en círculos externos (como frameworks, bases de datos o la interfaz de usuario).:
Source code dependencies must only point inwards, towards the core of the system.
No element declared in an inner circle or layer may know anything whatsoever about an element or detail declared in an outer circle.
2. The 4 Concentric Circles
The system is organized into concentric layers with distinct roles:
Entities
The core of the application containing enterprise-wide business rules. They can be objects with domain methods or pure data structures, completely independent of infrastructure, databases, or frameworks.
Use Cases
Define the application-specific workflows. Their job is to orchestrate the flow of data to and from Entities, executing business rules to fulfill system requirements.
Interface Adapters
Act as a translation bridge. They convert data from the format convenient for Use Cases and Entities into the format required by external agents (and vice-versa). Controllers, Presenters, DTOs, and Repository Implementations live here.
Frameworks & Drivers
The outermost layer consisting of technical tools and details (Laravel, Symfony, MySQL, Redis, UI views). This layer should be kept as thin as possible, containing glue code and infrastructure drivers.
Conclusion
Clean Architecture provides us with an organized structure where the core business logic remains shielded from external technical changes, enabling fast unit testing and long-term maintainability. In practical guides, we will see how to implement these concepts in frameworks like Laravel.