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>
2.1 KiB
2.1 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 | messaging-inbox-jdbc-postgresql-c04 | action 예외가 예약까지 함께 롤백시킨다 | state-machines-and-ownership | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:messaging-inbox-jdbc-postgresql-c04 | 2026-09-01 |
|
|
|
messaging-inbox-jdbc-postgresql |
action 예외가 예약까지 함께 롤백시킨다
수신 처리와 실패와 보존 세 경로가 있고, 실패 경로에서 롤백이 예약도 함께 되돌린다.
관계
- 컬럼 폭은 애플리케이션 검증과 짝을 이룬다 같은 분석 리프에서 끌어낸 규칙이다.
- 같은 안전 규칙은 한 공식과 한 강제 시점을 갖는다 같은 분석 리프에서 끌어낸 규칙이다.
본문
수신 처리 — handleOnce(name, delivery, action) → consumer.runOnce(messageId, name, now, () -> { action.apply(delivery); return APPLIED; }) → runner가 트랜잭션 열기 → repository.reserve(...) → 세 검사 → INSERT … ON CONFLICT DO NOTHING → 1행이면 부작용 실행, 0행이면 duplicate() → 커밋 → HandleResult.success().
실패 — action 예외 → ActionFailedException → runner가 롤백(예약도 함께) → HandleResult.Retry("INBOX_ACTION_FAILED").
보존 — cleanupJob.runOnce(now) → policy.cutoff(now) → 무제한 DELETE 1회 → 두 번째 호출 0 → 종료.
ActionFailedException 참조 위치
:::evidence key="messaging-inbox-jdbc-postgresql-c04" alt="코드베이스에서 ActionFailedException 를 검색한 출력 4줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="ActionFailedException 코드베이스 검색 — 4줄 · exit 0" zoom="true" :::