create-use-case

A use case in hexagonal architecture orchestrates domain entities without embedding core business logic. Define explicit request and response models to ensure testable workflows and strict separation between application, domain, and infrastructure layers.

In domain-driven design, a use case coordinates entities and applies application-level rules. It acts as a clean orchestrator that ensures essential business logic remains isolated within the domain layer rather than the application layer.

Generate a testable use case scaffold by defining explicit input and output models. Apply a recommended folder structure under application/use-cases and include unit tests to validate orchestration workflows across your application layer.

No, you should not use ORM frameworks inside hexagonal architecture use cases. The approach enforces no framework coupling and no ORM usage to maintain clean separation between domain logic and infrastructure layers.

Yes, this use case approach requires explicit input and output models. Defining Request and Response models enables straightforward testing and integration across the domain, application, and infrastructure layers.