spring-boot-conventions

What problem does it solve?

Inconsistent backend coding patterns across the Spring Boot project lead to maintainability challenges and team friction. This guide defines standard architecture, package structure, and class patterns to keep the codebase predictable and easier to onboard.

Core Features & Use Cases

• Enforces a three-layer architecture: Controller → Service → Repository.
• Standardizes package layout: config/, controller/, dto/, entity/, enums/, repository/, service/.
• Promotes specific class patterns: Entities with Lombok, Enums as STRING, DTOs as Java records, and repositories with clear query methods.
• Provides guidelines for DTOs, repositories, services, and controllers to avoid common anti-patterns and drift.

Quick Start

Start by structuring any new Java class to the com.aidonormatcher.backend layout and applying the three-layer pattern.