simple-kotlin-spring

A lean Kotlin Spring Boot architecture skips domain repository interfaces by injecting Spring Data XJpaRepository directly into handlers, keeping JPA entities responsible for domain mapping through toDomain and fromDomain methods.

Structure a Spring Boot multimodule MVP using buildingBlocks, core, presenter-api, presenter-consumer, and presenter-job modules to enforce a clean layout while keeping the domain layer simplified for rapid prototyping.

Use a repository-less DDD-lite approach in Spring Boot for MVPs and small team prototypes where faster delivery matters more than strict decoupling, accepting tighter core-to-infrastructure coupling in exchange for removing domain repository artifacts.

Yes, JPA entity mapping persists without a domain repository interface by implementing toDomain and fromDomain conversion methods directly on the JPA entity, preserving the persistence boundary while removing RepositoryImpl artifacts.

Injecting XJpaRepository directly into handlers accelerates MVP prototyping by removing repository boilerplate, but creates tighter coupling between core and infrastructure layers, making it unsuitable for complex, large-scale applications.