jpa-patterns

Use for data modeling, repositories, and performance tuning in Spring Boot. Enable auditing: For cursor-like pagination, include id > :lastId in JPQL with ordering. Recommended properties: For PostgreSQL LOB handling, add: Remember : Keep entities lean, queries intentional, and transactions short. Prevent N+1 with fetch strategies and projections, and index for your read/write paths. - Designing JPA entities and table mappings - Defining relationships (@OneToMany, @ManyToOne, @ManyToMany) - Optimizing queries (N+1 prevention, fetch strategies, projections) - Configuring transactions, auditing, or soft deletes - Setting up pagination, sorting, or custom repository methods - Tuning connection pooling (HikariCP) or second-level caching - Default to lazy loading; use JOIN FETCH in queries when needed - Avoid EAGER on collections; use DTO projections for read paths - Use projections for lightweight queries: - Annotate service methods with @Transactional - Use @Transactional(readOnly = true) for read paths to optimize - Choose propagation carefully; avoid long-running transactions - Add indexes for common filters ( status , slug , foreign keys) - Use composite indexes matching query patterns ( status, created_at ) - Avoid select * ; project only needed columns - Batch writes with saveAll and hibernate.jdbc.batch_size - 1st-level cache is per EntityManager; avoid keeping entities...