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.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 | adapter-outbound-httpclient-c08 | 전송의 선언이 프로파일보다 약하면 startup이 실패한다 | admission-budget-and-backpressure | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:adapter-outbound-httpclient-c08 | 2026-09-01 |
|
|
|
adapter-outbound-httpclient |
전송의 선언이 프로파일보다 약하면 startup이 실패한다
TransportCapabilityValidator가 프로파일이 요구하는 것과 전송이 선언한 것을 대조해 부족분을 이름으로 모아 거부한다. 메시지는 프로파일 설정과 능력 이름만 담고 URL·주소·비밀은 담지 않는다.
본문
TransportCapabilityValidator가 프로파일이 요구하는 것과 전송이 선언한 것을 대조해 부족분을 이름으로 모아 거부한다 — 프로토콜, route pool, 유계 pending 큐, proxy, mutual TLS, 동적 대상 안정성. 메시지는 "profile settings and capability names only — never a URL, address, or secret."
능력이 데이터로 선언된다
ReactiveTransportCapabilities.reactorNetty()는 9개 능력을 전부 true로, jettyHttp3Experimental()은 route pool·유계 큐·DNS 핀·동적 안정성을 false로 선언한다. HTTP/3는 compileOnly 의존이라 클래스가 없으면 Http3CapabilityReport가 전송을 거부한다 — "the failure mode is a startup error rather than a NoClassDefFoundError mid-call"(§0).
TransportCapabilityValidator 참조 위치
:::evidence key="adapter-outbound-httpclient-c08" alt="코드베이스에서 TransportCapabilityValidator 를 검색한 출력 11줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="TransportCapabilityValidator 코드베이스 검색 — 11줄 · exit 0" zoom="true" :::
testkit이 별도 source set인 이유
계약을 담은 클래스 35개(BlockingTransportContract·ReactiveTransportContract·RetrySafetyContract·ResourceLifecycleContract·ObservabilityContract·DynamicTargetSecurityContract)를 test·performance·jmh 세 lane이 공유한다. NettyLeakDetectionExtension은 leak detector 레벨을 믿지 않고 확인한다 — "asserts the level rather than trusting the flag reached the forked JVM"(§0).
성능 lane이 재지 않는 것
성능 lane 7개는 자원 상한을 검증한다 — PoolSaturationPerformanceTest·RetryStormBudgetTest·RuntimeRotationDrainTest·OAuthRefreshContentionTest·LargeBodyResourceTest·Http2StreamSaturationTest. §15에서 남긴 질문(ObjectBody.replayability()의 반사 비용을 재는 lane이 있는가)의 답은 없다 — 풀·재시도·회전·토큰 경합·본문 크기·H2 스트림을 재고 본문 재생 가능성 판정 비용은 재지 않는다.