typescript-hexagonal-architecture

To enforce hexagonal architecture in TypeScript, organize code into core/domain, core/ports, application use-cases, and infrastructure adapters. This enforces explicit dependency rules and one-way data flow from the domain outward through adapters.

Separate domain logic from infrastructure by defining explicit ports and implementing infrastructure adapters. This approach enforces clear module boundaries and ensures your core domain logic remains isolated from external dependencies.

Structure module boundaries by placing domain logic, ports, and adapters in clearly defined folders, then expose modules through barrel files. This enforces strict separation of concerns and explicit dependency direction across layers.

Yes, you can apply DDD principles by restructuring your application into core/domain, application use-cases, and infrastructure layers. This enforces explicit module boundaries and dependency rules without breaking existing domain logic.

Hexagonal architecture requires tests across domain, application use-cases, and infrastructure adapters to prevent regressions. This testing discipline validates the isolated domain logic and verifies adapter implementations against explicit ports.

Avoid hexagonal architecture when your module requires minimal separation of concerns or lacks complex domain logic. The overhead of explicit ports, adapters, and strict module boundaries is unnecessary for simple, isolated utility scripts.