multi-module-reference

Structure a Kotlin multi-module architecture by defining explicit module responsibilities for api, admin, batch, domain, and infra layers. Use Domain↔Infra mapping patterns with explicit ports and sample Gradle dependencies to establish clear boundaries and dependency mapping.

Organize Gradle KTS dependencies by aligning them with module responsibilities across domain, infra, and client-external layers. Use the canonical blueprint to map Gradle configurations, ensuring explicit ports and infra scaffolding examples scale correctly when adding new domains.

Domain to Infra mapping works by defining Port and Entity relationships within the Kotlin multi-module project. When adding new modules, you scaffold the infra layer based on domain ports, maintaining clear dependency mapping and module boundaries throughout the architecture.

Yes, you can use this multi-module architecture reference for code reviews. It provides a canonical blueprint to verify module boundaries, check Domain↔Infra mapping patterns, and validate package structure and Gradle dependencies against the expected layering.

Separate batch and admin modules when their module responsibilities require distinct entry points and dependency mappings within the multi-module architecture. The reference blueprint defines specific layer responsibilities for api, admin, batch, and common layers to maintain proper separation.

Define explicit ports between domain and infra layers to enforce strict module boundaries and dependency mapping within the Kotlin multi-module architecture. This pattern ensures the domain layer remains isolated, allowing infra scaffolding to implement ports without coupling.