springboot-patterns

This skill serves as a comprehensive architectural blueprint and implementation guide for developers building production-grade services with Java Spring Boot. It provides standardized patterns for structuring scalable backends, ensuring that codebases follow professional conventions such as the controller-service-repository layered architecture. The agent acts as a technical advisor for Spring MVC and WebFlux, helping developers translate business requirements into robust, maintainable API endpoints while adhering to strict validation and security standards.

• Standardized REST API design using @RestController, @Validated, and proper ResponseEntity response structures.

• Repository pattern implementation for Spring Data JPA, including custom @Query definitions and pagination/sorting configurations.

• Service layer design patterns emphasizing @Transactional boundary management and service-to-repository orchestration.

• DTO pattern strategies, including mapping logic, @Valid annotation usage, and Java Records for immutable data transfer.

• Global exception handling via @ControllerAdvice to standardize error responses and improve API reliability.

• Performance optimization techniques, including @Cacheable/@CacheEvict for distributed caching and @Async for non-blocking asynchronous task execution.

• Production-ready observability via SLF4J logging, diagnostic request logging filters, and retry logic for external integration calls.

• Comprehensive input handling, incorporating data integrity constraints, @FutureOrPresent checks, and robust error logging for internal service failures.

• The skill is intended for backend engineers and architects focusing on enterprise Java applications.

• Use this for refactoring monolithic services, implementing new microservices, or establishing a consistent codebase style across teams.

• Ensure your application has the necessary dependencies for JPA, Validation, and Caching before invoking specific patterns.

• Inputs typically involve domain entities, business logic requirements, or API endpoint specifications; outputs are clean, testable Java code snippets.

• Constraints include maintaining compatibility with the specific Spring Boot version in use; always verify compatibility for legacy versions of Spring framework before implementing advanced features like WebFlux or reactive patterns.