spring-boot-code-review

Check that @Transactional is applied at the service layer, not on controllers, and watch for self-invocation, private methods, and unchecked exception rollback rules that silently disable transactions. This review flags these transaction failure patterns with file locations and fixes.

Cover layering and Controller responsibilities, transaction boundaries, N+1 queries and pagination in JPA, authentication and parameter validation, exception swallowing, log masking, timeouts and retries, idempotency, migrations, and test gaps. Findings should be ranked by correctness, security, and data integrity.

Look for repository calls inside loops, lazy-loaded associations accessed after the session context, and missing fetch joins or entity graphs. The review inspects JPA usage patterns and reports N+1 risks along with pagination concerns.

Yes, it examines authentication and authorization coverage on endpoints, parameter validation, and log masking of sensitive data. Security findings are ranked near the top of the severity ordering.

Style preferences should not be reported as high-priority problems because they dilute attention from correctness and security defects. This review explicitly deprioritizes stylistic opinions and focuses on functional and operational risk.