Files
clean-architecture-backend-…/docs/jpa/support-matrix.md
T
donghyeon-kaandClaude Opus 5.5 0ed7bc8df7 review-followup Wave 3 라운드 1(P16): 빌드 게이트 정리 — JPA evidence manifest 폐기, build-tools 제거, API surface를 leaf check로
- 결정 4: JPA evidence·qualification manifest 폐기 → persistence-jpa 테스트, build-tools included build 비움(verifyEnvKeys는
  app-bootstrap 태스크, 구현은 build-logic `ca.config-contract`), gRPC release gate 삭제
- 결정 20: API surface 검사를 leaf `check`로, JPA adopter 검사를 `ca.api-surface`로 합침(구현 하나)
- 레인 단계 정리(문서 대조 레인은 `mainStage()`), integrationCheck가 입력 없는 레인을 이름과 함께 제외 → 로컬 통과(NEW-16)
- release workflow 통합, releaseCheck는 tag 전용, build-logic 비핵심 플러그인 정리, sample을 ArchUnit 대상에
- 보류 4행(B3 변경 모듈만 실행, C 이미지 서명, messaging 카드 검증 이동 2행 — 결정 필요), 남음 2행(O3-5 나머지)
- 통합: P17이 옮긴 gRPC release gate 사본 삭제, `grpc-proto-buf`를 release-gate needs에(P17-new-3)

검증: ./gradlew ci verifyDependencyLocks --warning-mode=fail 통과(685 task), mainCheck 통과(268 task),
-p optional-platforms ci 통과, -p build-logic test 78건 통과(손상된 TestKit 캐시 삭제 후)

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-09-28 16:44:17 +09:00

8.2 KiB

JPA Persistence Platform — Support Matrix

This document is a rendering. The machine-readable source is src/config/jpa/release-registry.json.

JpaReleaseManifest used to parse this file with regular expressions: every PostgreSQL NN it mentioned became a supported version, whatever table or sentence produced the match. An Experimental major joined the Stable list, a version named once in prose counted as supported, and demoting a major changed nothing so long as the string survived somewhere in the document. Now the registry declares a support level per major as a field, each gate names the Gradle task that produces its evidence, and this document describes what the registry says.

Being a rendering used to be a claim rather than a mechanism: the tables below were still typed by hand, so a major demoted in the registry stayed Stable here and kept its full release job. JpaReleaseRenderingTest now compares the database table, the gate table and release.yml's JPA matrix and promotion lists to the registry, and the jpaReleaseQualification aggregate depends on every blocking gate's task, so a gate naming a task that does not exist fails when the task graph is built. Edit the registry; these tables follow, or the build fails.

Two renderings stayed outside that comparison until they were added to it. jpa-nightly.yml runs its own matrix and nothing checked it, so a demotion corrected the release lane and left the nightly lane certifying the major. And an Experimental major's "compatibility lane only" named no file: the lane existed, but the registry, this document and the release workflow could each be read end to end without establishing that, so a reader looking for it concluded there was none. An Experimental major now has to be recorded as the target of a lane in .github/workflows, and a Stable lane may not run it.

Database

Database Support Evidence
PostgreSQL 16 Stable full contract suite, release lane (own matrix job)
PostgreSQL 17 Stable full contract suite, release lane (own matrix job)
PostgreSQL 18 Stable full contract suite, release lane (own matrix job)
PostgreSQL 19 Experimental jpa-next.yml — NOT_EXECUTABLE: no postgres:19-alpine is published, so no container of that major has been started; promotion requires an ADR
H2 Local convenience never evidence of PostgreSQL behaviour

Each major gets its own release job, because for a while it did not. The release lane passed -Pjpa.matrix.versions=16,17,18 to a JpaPlatformContractSupport.start() that used selectedVersions().get(0), so the whole integration suite ran against PostgreSQL 16 and this table recorded 17 and 18 as fully covered on the strength of a three-assertion smoke test. start() now refuses a multi-version selection outright, the jpa-release-gate job in release.yml fans out to one job per major, and a promotion job requires all three majors' evidence to carry the same commit SHA — so a removed major removes the release, not the evidence for it.

Provider baseline. The gates run against the Hibernate version the Spring Boot BOM resolves — 7.1.8.Final — which the registry records as stable-tested-baseline. This document previously called 7.4 the Stable baseline and the pagination gate was named hibernate-7.4-fetch-pagination, so every run of that gate produced evidence labelled with a provider it had never executed against. 7.4 is recorded as compatibility-target; it becomes the baseline when a full lane has actually run on it.

H2 is not a second production target. It reports different SQLSTATEs for the same violation, no JSONB operators, no range types, and no concurrent index builds. A green H2 run is evidence that the code compiles and runs, and nothing more.

SKIP LOCKED needs its own sentence, because two documents said different things about it. The module's CLAUDE.md records a measurement: H2 2.4.240 accepts FOR UPDATE SKIP LOCKED and does genuinely skip locked rows, which is why the outbox claim SQL is identical on both vendors. This document previously said H2 has no such guarantee. Both are right about different questions, and the distinction is the point: observed behaviour in the version we measured is not a production guarantee, and it is never PostgreSQL contract evidence. The measurement is why the claim SQL needs no vendor branch; the absence of a guarantee is why every concurrency contract still runs against a real PostgreSQL.

Specification and provider

Component Stable Experimental
Jakarta Persistence 3.2 4.0 (lane)
Hibernate ORM 7.4 declared baseline 8 (lane)
Spring Boot repository BOM —

The Hibernate row needs a note. The design declares 7.4 as the Stable provider; this repository's Spring Boot BOM resolves 7.1.x. HibernateProviderPolicy holds both — the declared baseline as a constant, the resolved version read from Hibernate itself — and driftsFromDeclaredBaseline() makes the difference visible instead of asserting a constant against itself. See repository-adaptation.md §4.

Capability support levels

The levels are the ones JpaPlatformAutoConfiguration.capabilities() reports through the jpaplatform actuator endpoint. Advanced and Experimental rows are library code a service calls itself (src/adapter/outbound/persistence-jpa/README.md "라이브러리 API").

Capability Level
Keyset pagination Stable
Flyway schema gate Stable
Runtime role verification Stable
Commit completion evidence Advanced
JDBC batch Advanced
Observability (query metrics, redaction) Advanced
PostgreSQL JSONB Advanced
PostgreSQL array and range Advanced
Bulk DML Advanced
Hibernate StatelessSession Advanced
PostgreSQL COPY Admin (J4)
Hibernate second-level cache Advanced
Hibernate Envers Advanced
Technical auditing — audit/AuditableEntity Stable (canonical)
Multi-tenancy (column, RLS, schema, database) Experimental
Consistency-aware read replica Experimental

Release gates

Each row is a way the platform could pass its tests and still be wrong in production.

Gate Kind What it prevents
postgresql-contract gate a release whose only database evidence came from H2
completion-unknown-no-retry gate automatically re-running a write that may already have committed
osiv-disabled gate lazy loading from the view layer, one query per rendered row
flyway-validate gate Hibernate mutating a deployed schema, or running against one it was not built for
runtime-role-no-ddl gate the application's own credential being able to alter or drop schema objects
collection-fetch-pagination gate a paged collection fetch silently reading the whole table and paginating in memory

The audit mechanism

audit/AuditableEntity is the only one: created_*/updated_*, a 256-character actor, stamped explicitly by the repository adapter. It is what the sample entities extend and what the migrations were written for. A second, Spring Data listener-based mechanism (auditing/AuditMetadata) was never composed and has been removed; JpaAuditMechanismRule.entitiesUseExactlyOneAuditMechanism keeps it from coming back on an entity.

The mechanism does not reach a bulk or native update. It stamps on an ordinary save in the adapter, so a statement that goes straight to the database leaves the audit columns showing the previous save. A bulk update of an audited entity must therefore set the audit column in the statement, which JpaAuditMechanismRule.bulkUpdatesOfAuditedEntitiesStampAudit checks over the production graph.

Explicitly unsupported

  • Reactive JPA. JPA is a blocking specification; a reactive facade over it moves the blocking call onto an event loop rather than removing it.
  • Hibernate as the production schema writer. ddl-auto never mutates a deployed schema.
  • A platform-owned generic CRUD repository. Domains own their repositories (design §10.1).
  • Automatic reconciliation of a completion-unknown transaction. The platform records; the domain resolves.