hexagonal-architecture

To enforce hexagonal architecture in Kotlin bounded contexts, apply rules that audit core purity, port patterns, adapter boundaries, and transaction boundaries. This ensures strict dependency direction on the core and keeps business logic framework-free.

The recommended module structure for hexagonal architecture in Kotlin assigns each entity clear modules: core, in, out, persistence, and itest. This organization enforces strict dependency direction on the core and separates outbound and inbound port contracts.

Yes, you can review PRs for ports and adapters architectural compliance. The rules audit core purity, port patterns, and persistence organization to ensure cross-context wiring and application composition align with hexagonal architecture best practices.

You need to apply hexagonal architecture rules when creating new bounded contexts or wiring cross-context dependencies. It is also applicable when defining gateway patterns, orchestrators, and test architecture to support end-to-end flows.

The best way to keep Kotlin business logic framework-free using ports and adapters is enforcing strict transaction boundary ownership. Defining clear outbound and inbound port contracts ensures the core domain remains isolated from external dependencies.

Yes, hexagonal architecture auditing checks transaction boundaries and persistence organization. It validates that transaction boundary ownership is strictly maintained and that persistence modules align with the defined dependency direction on the core.