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.9 KiB
2.9 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-inbound-graphql-c04 | 다섯 예산 계층 중 요청 계층만 배선돼 있다 | admission-budget-and-backpressure | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:adapter-inbound-graphql-c04 | 2026-09-01 |
|
|
|
adapter-inbound-graphql |
다섯 예산 계층 중 요청 계층만 배선돼 있다
설계 §10이 다섯 계층을 정의하고 GraphQlDeadlinePropagator가 그 파생을 담는다. 실제로 배선된 것은 요청 계층 하나이고, 나머지 파생 메서드는 프로덕션 호출자가 없다.
본문
설계 §10이 다섯 계층을 정의하고 GraphQlDeadlinePropagator가 그 파생을 담는다. 실제 강제 상태는 이렇다.
| 계층 | 파생 지점 | 배선 |
|---|---|---|
| 전송 핸드셰이크 | — | (이 sub-scope 밖) |
| 요청 | GraphQlPlatformWebInterceptor:135 — GraphQlDeadline.after(policy.maxExecutionTime(), clock) |
예 |
| 리졸버 | GraphQlDeadlinePropagator.resolverBudget(...) |
아니오 |
| DataLoader 배치 | GraphQlDeadlinePropagator.dataLoaderBatchTimeout(...) |
아니오 |
| 다운스트림(DB/HTTP) | GraphQlDeadlinePropagator.downstreamDeadline(...) |
아니오 |
| 구독 연결 | GraphQlDeadlinePropagator.subscriptionDeadline(...) |
아니오 |
요청 예산에서 파생되는 계층
:::evidence key="adapter-inbound-graphql-c04-diagram" alt="배선된 요청 데드라인 상자에서 나가는 화살표가 없고, 네 파생 계층이 파생 없음 이라고 이름 붙은 별도 영역 안에 빗금으로 놓인 구조" caption="요청 예산에서 파생되는 계층" zoom="false" :::
참조가 갇혀 있는 범위
GraphQlTimeoutPolicy와 GraphQlResolverBudget의 main 참조자를 전수하면 전부 execution 패키지 안(그리고 미배선 클러스터 안)이다.
GraphQlTimeoutPolicy <- GraphQlRequestCancelledException, GraphQlDeadlinePropagator, GraphQlResolverBudget
GraphQlResolverBudget <- GraphQlResolverDescriptor, GraphQlResolverCatalog, GraphQlDeadlinePropagator, GraphQlExecutionProfileValidator
§12.1.
GraphQlDeadlinePropagator 참조 위치
:::evidence key="adapter-inbound-graphql-c04" alt="코드베이스에서 GraphQlDeadlinePropagator 를 검색한 출력 5줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="GraphQlDeadlinePropagator 코드베이스 검색 — 5줄 · exit 0" zoom="true" :::