java-coding-standard

Enforce Java coding standards during Spring Boot code reviews by checking naming conventions, immutability patterns, Optional usage, streams, and exception handling to catch violations early and improve reliability. Apply these checks to pull requests and during onboarding.

Java Spring Boot naming conventions require classes in PascalCase, methods and fields in camelCase, and constants in UPPER_SNAKE_CASE. Apply these rules to maintain consistency and readability across modules during code reviews.

Use Optional in Spring Boot to handle absence of values explicitly and switch to reactive patterns where appropriate. Prefer records and final fields for immutability, avoiding setters unless required by framework bindings.

The best way to handle exceptions in Spring Boot codebases is using targeted exception types with meaningful messages. Avoid broad catch blocks to ensure maintainability and reliability across services.

Favor concise streams for data transformations in Java Spring Boot services. Using streams improves readability and maintainability when processing collections, aligning with standard coding practices.

You can apply these Java coding standards to existing Spring Boot codebases during onboarding and code reviews. Trace and enforce practices across services to detect violations early and ensure new modules adhere to guidelines.