Catalog
affaan-m/jpa-patterns

affaan-m

jpa-patterns

JPA/Hibernate patterns for entity design, relationships, query optimization, transactions, auditing, indexing, pagination, and pooling in Spring Boot. Use when designing JPA entities or relationships, or when a Hibernate query, transaction, or N+1 problem needs fixing.

NewUpdated Sep 9, 2026

JPA/Hibernate Patterns

Use for data modeling, repositories, and performance tuning in Spring Boot.

When to Activate

  • 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

Entity Design

@Entity
@Table(name = "markets", indexes = {
  @Index(name = "idx_markets_slug", columnList = "slug", unique = true)
})
@EntityListeners(AuditingEntityListener.class)
public class MarketEntity {
  @Id @GeneratedValue(strategy = GenerationType.IDENTITY)
  private Long id;

  @Column(nullable = false, length = 200)
  private String name;

  @Column(nullable = false, unique = true, length = 120)
  private String slug;

  @Enumerated(EnumType.STRING)
  private MarketStatus status = MarketStatus.ACTIVE;

  @CreatedDate private Instant createdAt;
  @LastModifiedDate private Instant updatedAt;
}

Enable auditing:

@Configuration
@EnableJpaAuditing
class JpaConfig {}

Relationships and N+1 Prevention

@OneToMany(mappedBy = "market", cascade = CascadeType.ALL, orphanRemoval = true)
private List<PositionEntity> positions = new ArrayList<>();
  • Default to lazy loading; use JOIN FETCH in queries when needed
  • Avoid EAGER on collections; use DTO projections for read paths
@Query("select m from MarketEntity m left join fetch m.positions where m.id = :id")
Optional<MarketEntity> findWithPositions(@Param("id") Long id);

Repository Patterns

public interface MarketRepository extends JpaRepository<MarketEntity, Long> {
  Optional<MarketEntity> findBySlug(String slug);

  @Query("select m from MarketEntity m where m.status = :status")
  Page<MarketEntity> findByStatus(@Param("status") MarketStatus status, Pageable pageable);
}
  • Use projections for lightweight queries:
public interface MarketSummary {
  Long getId();
  String getName();
  MarketStatus getStatus();
}
Page<MarketSummary> findAllBy(Pageable pageable);

Transactions

  • Annotate service methods with @Transactional
  • Use @Transactional(readOnly = true) for read paths to optimize
  • Choose propagation carefully; avoid long-running transactions
@Transactional
public Market updateStatus(Long id, MarketStatus status) {
  MarketEntity entity = repo.findById(id)
      .orElseThrow(() -> new EntityNotFoundException("Market"));
  entity.setStatus(status);
  return Market.from(entity);
}

Pagination

PageRequest page = PageRequest.of(pageNumber, pageSize, Sort.by("createdAt").descending());
Page<MarketEntity> markets = repo.findByStatus(MarketStatus.ACTIVE, page);

For cursor-like pagination, include id > :lastId in JPQL with ordering.

Indexing and Performance

  • 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

Connection Pooling (HikariCP)

Recommended properties:

spring.datasource.hikari.maximum-pool-size=20
spring.datasource.hikari.minimum-idle=5
spring.datasource.hikari.connection-timeout=30000
spring.datasource.hikari.validation-timeout=5000

For PostgreSQL LOB handling, add:

spring.jpa.properties.hibernate.jdbc.lob.non_contextual_creation=true

Caching

  • 1st-level cache is per EntityManager; avoid keeping entities across transactions
  • For read-heavy entities, consider second-level cache cautiously; validate eviction strategy

Migrations

  • Use Flyway or Liquibase; never rely on Hibernate auto DDL in production
  • Keep migrations idempotent and additive; avoid dropping columns without plan

Testing Data Access

  • Prefer @DataJpaTest with Testcontainers to mirror production
  • Assert SQL efficiency using logs: set logging.level.org.hibernate.SQL=DEBUG and logging.level.org.hibernate.orm.jdbc.bind=TRACE for parameter values

Remember: Keep entities lean, queries intentional, and transactions short. Prevent N+1 with fetch strategies and projections, and index for your read/write paths.

Files1
1 files · 1.0 KB

Select a file to preview

Overall Score

86/100

Grade

A

Excellent

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

88

Quality

88

Clarity

85

Completeness

80

Summary

A Spring Boot JPA/Hibernate patterns guide covering entity design, relationships, query optimization, transactions, pagination, and connection pooling. It provides concrete code examples for common data modeling tasks and includes performance tuning recommendations for N+1 prevention and caching strategies.

Detected Capabilities

code example provisiondata model guidancequery pattern documentationconfiguration recommendationperformance tuning instruction

Trigger Keywords

Phrases that agents use to match this skill to user intent.

jpa entity designspring boot data layerhibernate n+1 fixjpql query optimizationspring data repositorydatabase indexing strategyconnection pool tuning

Use Cases

  • - Design JPA entities with auditing, enums, and proper constraint annotations - Define and optimize OneToMany/ManyToMany/ManyToOne relationships with lazy loading and fetch strategies - Implement custom repositories with JPQL queries, projections, and pagination - Fix N+1 query problems using JOIN FETCH and projection-based reads - Configure HikariCP connection pooling and Hibernate caching strategies - Set up soft deletes, timestamps, and database indexing for query performance - Write transactional service methods with read-only optimization - Debug query performance using Hibernate SQL logging and Testcontainers

Quality Notes

  • - Well-organized sections with clear use-case triggers and practical Java examples - Code examples are idiomatic and follow Spring Boot conventions (annotations, lazy-loading defaults) - Performance guidance is specific and actionable (JOIN FETCH patterns, projection use, batch configuration) - Includes configuration properties with recommended values (HikariCP pool size, timeouts) - Good coverage of common pitfalls (N+1 queries, EAGER on collections, long-running transactions) - Testing guidance tied to actual debugging (DEBUG logging, Testcontainers integration) - Migrations section correctly emphasizes idempotency and caution with Hibernate auto-DDL - Caching guidance appropriately cautious about first-level cache lifecycle and second-level cache gotchas - Example entity uses modern JPA features (@EntityListeners, @CreatedDate, @LastModifiedDate)
Model: claude-haiku-4-5-20251001Analyzed: Sep 9, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Version History

  1. v2.0

    Contract changed: description

    ✦ AIExpands activation description to clarify when agents should use the skill: entity/relationship design, N+1 problems, query, and transaction fixes.

    triggering2026-09-09

    LATEST
  2. v1.2

    Content updated

    ✦ AISKILL.md content and supporting files unchanged; safety grade moved to B.

    2026-07-14

    View This Version
  3. v1.1

    Content updated

    ✦ AIAdds LICENSE file.

    2026-04-20

    View This Version
  4. v1.0

    Seeded from github.com/affaan-m/everything-claude-code

    2026-03-16

    View This VersionInitial version

Use affaan-m/jpa-patterns in your dev environment

Command Palette

Search for a command to run...

affaan-m/jpa-patterns | SkillRepo