Files

T

DongHyeonkaandClaude Opus 5 b2963105a8 docs(keycloak-session-store): import the session-storage lab as a new project

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>

2026-09-04 22:51:59 +09:00

2.9 KiB

Raw Blame History

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-support-c01

허용된 의존과 실제 의존이 다르다

composition-and-lifecycle-models

clean-architecture-backend-template

게시 전

21234e38cdb9a926cbc92bb97a2aee2e4a7d2916

concept:adapter-outbound-support-c01

2026-09-01

key	file
adapter-outbound-support-c01	../../../final/evidence/rendered/adapter-outbound-support-c01.svg

key	file
adapter-outbound-support-c01-diagram	../../../final/assets/diagrams/adapter-outbound-support-c01.svg

../../../final/evidence/raw/adapter-outbound-support-c01.txt

원본 분석 절은 analysis/04-adapter-outbound-support.md#L52 이다.

adapter-outbound-support

허용된 의존과 실제 의존이 다르다

adapter-outbound-support의 프로덕션 표면은 타입 셋뿐이다. 레지스트리가 허용하는 project dependency는 셋이지만 실제 project dependency는 0개다.

본문

adapter-outbound-support는 application port를 구현하는 하나의 기술 adapter라기보다 여러 outbound adapter가 공유할 수 있는 기술적 보조 seam이다.

이 리프의 프로덕션 표면

:::evidence key="adapter-outbound-support-c01-diagram" alt="리프 경계 안에 상관 식별자 조회와 fail-open 로거와 기본 bean 설정 세 상자가 나란히 들어 있는 구조" caption="이 리프의 프로덕션 표면" zoom="false" :::

OutboundCorrelation은 SLF4J MDC에서 correlation_id를 조회하고 값이 없거나 blank면 "unknown"을 반환한다. FailOpenDependencyLogger는 optional/fail-open outbound 호출의 success/failure observation을 공통 포맷으로 기록한다 — success는 DEBUG, failure는 WARN이다. OutboundSupportConfig는 FailOpenDependencyLogger default bean을 제공하고, @ConditionalOnMissingBean으로 fork/application이 같은 타입을 override할 수 있게 한다.

OutboundCorrelation 참조 위치

:::evidence key="adapter-outbound-support-c01" alt="코드베이스에서 OutboundCorrelation 를 검색한 출력 15줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="OutboundCorrelation 코드베이스 검색 — 15줄 · exit 0" zoom="true" :::