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-transport-spi-c06 | 두 자료구조가 다른 방식으로 보호되고 주석이 없다 | state-machines-and-ownership | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:messaging-transport-spi-c06 | 2026-09-01 |
|
|
|
messaging-transport-spi |
두 자료구조가 다른 방식으로 보호되고 주석이 없다
이 leaf는 messaging family에서 동시성 밀도가 가장 높다. current는 lock-free로, draining은 synchronized로 다룬다.
관계
- 멱등 종료를 보장하는 컴포넌트는 종료 이후의 등록도 정의한다 같은 분석 리프에서 끌어낸 규칙이다.
- 같은 개념의 sentinel은 계층을 넘어 하나로 정한다 같은 분석 리프에서 끌어낸 규칙이다.
본문
이 leaf는 messaging family에서 동시성 밀도가 가장 높다.
DefaultMessagingRuntimeRegistry 참조 위치
:::evidence key="messaging-transport-spi-c06" alt="코드베이스에서 DefaultMessagingRuntimeRegistry 를 검색한 출력 25줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="DefaultMessagingRuntimeRegistry 코드베이스 검색 — 25줄 · exit 0" zoom="true" :::
두 자료구조가 다른 방식으로 보호된다
주목할 비대칭: DefaultMessagingRuntimeRegistry가 current는 lock-free(ConcurrentHashMap)로, draining은 synchronized ArrayList로 다룬다. draining은 회전 때만 접근하므로 경합이 없다 — 합리적 선택이지만 주석이 없다.
선언된 것과 실현된 것
수명주기는 §4.4의 8단계가 선언이고 §12.1이 실현 상태를 다룬다.