jpa-patterns

Topics in the source

• JPA/Hibernate Patterns
• When to Activate
• Entity Design
• Relationships and N+1 Prevention
• Repository Patterns
• Transactions
• Pagination
• Indexing and Performance

Use for data modeling, repositories, and performance tuning in Spring Boot. 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 Enable auditing: 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 For cursor-like pagination, include id > :lastId in JPQL with ordering. Add indexes for common filters (status, slug, foreign keys) Use composite indexes matching query patterns (status, createdat) Avoid select ; project only needed columns Batch writes with saveAll and hibernate.jdbc.batchsize Recommended properties: For PostgreSQL LOB handling, add: 1st-level cache is per EntityManager; avoid keeping entities across tran

This is an excerpt. Refer to the complete source and its current requirements.