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>
52 lines
2.1 KiB
Markdown
52 lines
2.1 KiB
Markdown
---
|
|
kind: CONCEPT
|
|
slug: adapter-outbound-persistence-jpa-c15
|
|
title: 한 번의 물리 시도만 담당하고 재시도는 하지 않는다
|
|
topic: transaction-and-consistency-models
|
|
project: clean-architecture-backend-template
|
|
status: 게시 전
|
|
sourceRevision: 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916
|
|
rootTreeNode: concept:adapter-outbound-persistence-jpa-c15
|
|
evidenceCapturedOn: 2026-09-01
|
|
assets:
|
|
- key: adapter-outbound-persistence-jpa-c15
|
|
file: ../../../final/evidence/rendered/adapter-outbound-persistence-jpa-c15.svg
|
|
evidence:
|
|
- ../../../final/evidence/raw/adapter-outbound-persistence-jpa-c15.txt
|
|
source:
|
|
- 원본 분석 절은 analysis/05-adapter-outbound-persistence-jpa.md#L953 이다.
|
|
module: adapter-outbound-persistence-jpa
|
|
---
|
|
|
|
# 한 번의 물리 시도만 담당하고 재시도는 하지 않는다
|
|
|
|
`SpringJpaTransactionExecutor`는 attempt boundary를 소유하고 raw provider exception을 `JpaPersistenceException`으로 바꾸는 위치다. 자체 retry는 하지 않는다.
|
|
|
|
## 본문
|
|
|
|
<!-- body:start -->
|
|
|
|
이 executor는 한 번의 physical attempt만 담당한다. 자체 retry는 하지 않는다.
|
|
|
|
```text
|
|
TransactionEvidenceContext.begin(...)
|
|
-> TransactionTemplate.execute(work)
|
|
-> success return
|
|
or
|
|
-> attempt boundary에서 failure translation
|
|
-> translated runtime exception rethrow
|
|
finally
|
|
-> TransactionEvidenceScope close
|
|
```
|
|
|
|
## SpringJpaTransactionExecutor 참조 위치
|
|
|
|
:::evidence key="adapter-outbound-persistence-jpa-c15" alt="코드베이스에서 SpringJpaTransactionExecutor 를 검색한 출력 26줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="SpringJpaTransactionExecutor 코드베이스 검색 — 26줄 · exit 0" zoom="true"
|
|
:::
|
|
|
|
## 이 자리가 번역 지점인 이유
|
|
|
|
attempt boundary에서 operation, attempt number, elapsed time, reconciliation key를 알고 있으므로 raw provider exception을 `JpaPersistenceException`으로 변환하는 위치로 사용된다. vendor translator가 조립되면 PostgreSQL 40001/40P01 같은 structured SQLSTATE가 stable exception으로 바뀌어 coordinator가 처리할 수 있다.
|
|
|
|
<!-- body:end -->
|