DongHyeonkaandClaude Opus 5
b2963105a8
The keycloak project ended with four open questions that design could not
settle. A two-VM lab was built to answer them by measurement, and this is
that material: 26 experiments, 125 raw command outputs, 22 browser captures.
Follows the import procedure in README.md.
source/ the originating repository verbatim — 78 documents, 28 SVGs,
8 manifests, plus .source-revision recording the commit
final/ the SSOT
document.md 729 lines written from the 29 experiment documents, not
concatenated: what was predicted, what was measured, and
where the measurement itself was wrong
evidence/raw 125 outputs, flattened to <experiment>__<file> because
the originals collided (01-baseline.txt appeared three
times) and the audit only globs the top level
evidence/meta one per raw file; command and exitCode are null and the
README says why rather than inventing them
evidence/browser 22 captures
assets/ three diagrams through techviz
.techviz/ their VizSpecs
A separate project rather than an addition to keycloak: the B-layer answers
that project's four questions, but the A, C and D layers are about cluster
failure, SSO and operations, and one document.md should hold one subject.
The four question records there can point here through 관계.
Recorded rather than papered over: only three of the 28 diagrams were
remade. The repository forbids hand-drawn SVG and forbids titles inside the
canvas; all 28 originals carry both, so converting them is redrawing, not
reformatting. They stay in source/ and the gap is written into the document.
verify-pipeline.py passes. audit-records.py reports no issues.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
3.3 KiB
kind, slug, title, topic, project, status, sourceRevision, rootTreeNode, evidenceCapturedOn, assets, evidence, source, module
| kind | slug | title | topic | project | status | sourceRevision | rootTreeNode | evidenceCapturedOn | assets | evidence | source | module | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CONCEPT | adapter-outbound-persistence-jpa-c02 | 능력 어휘와 지원 등급과 실제 보고를 나눈다 | transaction-and-consistency-models | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:adapter-outbound-persistence-jpa-c02 | 2026-09-01 |
|
|
|
adapter-outbound-persistence-jpa |
능력 어휘와 지원 등급과 실제 보고를 나눈다
JpaCapability enum은 16개 capability id를 갖고 app-bootstrap의 capabilities()도 16개를 선언한다. 능력 이름은 어휘일 뿐이고 CapabilitySupport가 등급을 결합하며 composition이 실제 보고를 구성한다.
본문
현재 enum은 16개 capability id를 갖는다. app-bootstrap의 JpaPlatformAutoConfiguration.capabilities() 역시 16개를 선언하므로 enum catalog와 current composition count는 일치한다.
Stable composition은 대표적으로 transaction retry, completion evidence, keyset pagination, batch, schema gate, runtime-role verification, observability를 기본 지원으로 보고한다. Advanced capability는 PostgreSQL native write/work claim/JSONB/array-range, bulk DML, stateless session, COPY, L2 cache, Envers 등을 constraints와 함께 보고한다.
보고 가능한 계약이 만들어지는 층
:::evidence key="adapter-outbound-persistence-jpa-c02-diagram" alt="능력 어휘와 지원 등급 결합과 실제 보고 구성이 위에서 아래로 쌓이고 보고 구성 화살표가 아래로 그려진 구조" caption="보고 가능한 계약이 만들어지는 층" zoom="false" :::
이 분리는 "classpath에 코드가 있다"와 "현재 composition이 기본 지원한다고 약속한다"를 동일시하지 않는다. capability enum은 vocabulary이고, CapabilitySupport가 support level을 결합하며, app-bootstrap composition이 실제 현재 report를 구성한다.
CapabilitySupport 참조 위치
:::evidence key="adapter-outbound-persistence-jpa-c02" alt="코드베이스에서 CapabilitySupport 를 검색한 출력 11줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="CapabilitySupport 코드베이스 검색 — 11줄 · exit 0" zoom="true" :::
생성자가 보장하는 것
capability non-null, level non-null, constraints list defensive copy, 각 constraint non-null / non-blank. usableByDefault()는 STABLE만 true다 — Advanced/Experimental이 "존재하므로 기본 사용 가능"으로 오해되지 않게 support level을 코드에 남긴다.
보고서가 담지 않는 것
JpaPlatformReport는 JDBC URL/user/password/SQL/entity catalog를 필드로 갖지 않도록 설계되어 있고, privilege detail도 boolean으로 축약한다. management endpoint의 reconnaissance surface를 좁히는 방향이다.