hexagonal-architecture

Hexagonal architecture separates domain logic from infrastructure by defining ports and adapters boundaries, ensuring infrastructure concerns do not leak into the core domain. This approach isolates business rules from external I/O operations during system design.

Defining ports and adapters boundaries involves mapping application services and external I/O interactions at the system edge. This architectural pattern maintains a strict separation between the domain core and infrastructure adapters to preserve testability.

No, hexagonal architecture guidance does not scaffold project files. It focuses on defining layering, naming conventions, and boundary verification, expecting users to utilize a separate scaffold skill for actual project file generation.

Evaluating component placement involves mapping design elements against domain, application, and adapter layers to verify boundaries. This ensures domain logic remains isolated and infrastructure components interact only through defined ports.

Use ports and adapters architecture when designing new systems that require testable boundaries and scalable structures. It is particularly useful for discussing domain logic in isolation and mapping adapters at the boundary to prevent infrastructure leakage.