hexagonal-architecture

Topics in the source

• Hexagonal Architecture
• When to Use
• Core Concepts
• How It Works
• Step 1: Model a use case boundary
• Step 2: Define outbound ports first
• Step 3: Implement the use case with pure orchestration
• Step 4: Build adapters at the edge

Hexagonal architecture (Ports and Adapters) keeps business logic independent from frameworks, transport, and persistence details. The core app depends on abstract ports, and adapters implement those ports at the edges. Building new features where long-term maintainability and testability matter. Refactoring layered or framework-heavy code where domain logic is mixed with I/O concerns. Supporting multiple interfaces for the same use case (HTTP, CLI, queue workers, cron jobs). Replacing infrastructure (database, external APIs, message bus) without rewriting business rules. Use this skill when the request involves boundaries, domain-centric design, refactoring tightly coupled services, or decoupling application logic from specific libraries. Domain model: Business rules and entities/value objects. No framework imports. Use cases (application layer): Orchestrate domain behavior and workflow steps. Inbound ports: Contracts describing what the application can do (commands/queries/use-case interfaces). Outbound ports: Contracts for dependencies the application needs (repositories, gateways, event publishers, clock, UUID, etc.). Adapters: Infrastructure and delivery implementations of port

This is an excerpt. Refer to the complete source and its current requirements.