How team-dodn/spring-boot-kotlin-template works
Project type and purpose
• This is a modular Kotlin/Spring Boot “template” monorepo designed to jump-start a microservice or API service.
• It provides a core executable service (core-api), shared enums (core-enum), example external client integrations (clients), database integration (storage), cross-cutting support (logging, monitoring), and test-support modules.
File structure
• Top-level modules:
• core/core-api – the main Spring Boot application providing REST APIs and domain services
• core/core-enum – reusable enum definitions shared across modules
• clients/client-example – sample OpenFeign HTTP client integration
• storage/db-core – Spring Data JPA integration with MySQL (entities, repositories, datasource configs)
• support/logging – centralized logging and distributed tracing setup (Sentry, Logback)
• support/monitoring – application monitoring configuration
• tests/api-docs – Spring REST Docs integration for API documentation
• Standard Gradle multi-module layout with build scripts, resources, and test suites under each module.
• Profiles and configuration files (application.yml, module-specific yml, gradle.properties).
README for additional insights
• Modules map to domain boundaries and cross-cutting concerns.
• Dependency versions are managed centrally in gradle.properties.
• Runtime profiles (local, dev, staging, live) align with external environment deployments.
• CI tasks and test tags indicate modular test strategies: unitTest, contextTest, restDocsTest, developTest.