principle-clean-architecture

To enforce the dependency rule in clean architecture, define ports in the domain layer and implement adapters in outer layers. This keeps source-code dependencies pointing inward so inner layers remain framework-agnostic and business logic stays independent.

Hexagonal architecture, or ports and adapters, separates interfaces (ports) from implementations (adapters) to make the domain testable and swappable. Outer layers translate across well-defined structures, ensuring the domain remains independent of infrastructure.

Prevent ORM and framework types from crossing boundaries by using translation structures to keep the domain pure. Ensure repositories do not return ORM objects and use cases do not import request/response types, detecting these drift smells during refactoring.

Decompose layers by proposing a breakdown into domain, application, infrastructure, and framework layers. Identify which components must become ports and adapters, ensuring dependencies flow inward and business logic stays independent of databases and external concerns.

Use clean architecture when planning architecture, decomposing layers, or refactoring use cases and repositories. It prevents architectural erosion by enforcing clean boundaries, making it ideal for systems requiring domain independence from frameworks, databases, and UI boundaries.

Common drift smells in clean architecture refactoring include repositories returning ORM objects and use cases importing HTTP request or response types. These violations indicate framework concerns are crossing boundaries, requiring translation structures to restore domain purity.