Files
document-haness/docs/clean-architecture-backend-template/tech-log-studio/schema-and-wire-models/concept/concept-adapter-outbound-persistence-mongo-c09.md
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

3.2 KiB


kind: CONCEPT slug: adapter-outbound-persistence-mongo-c09 title: @Configuration을 게이팅하면 게이트를 공급하는 것을 게이팅한다 topic: schema-and-wire-models project: clean-architecture-backend-template status: 게시 전 sourceRevision: 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 rootTreeNode: concept:adapter-outbound-persistence-mongo-c09 evidenceCapturedOn: 2026-09-01 assets:

  • key: adapter-outbound-persistence-mongo-c09 file: ../../../final/evidence/rendered/adapter-outbound-persistence-mongo-c09.svg evidence:
  • ../../../final/evidence/raw/adapter-outbound-persistence-mongo-c09.txt source:
  • 원본 분석 절은 analysis/06-adapter-outbound-persistence-mongo.md#L1269 이다. module: adapter-outbound-persistence-mongo

@Configuration을 게이팅하면 게이트를 공급하는 것을 게이팅한다

advanced 분류 불변식이 문서가 아니라 코드로 서 있고, 제외 항목마다 근거가 붙어 있다.

본문

세어 봤다(137-... §8.1b·§8.1c).

  • @MongoAdvancedEntryPoint 7개: MongoChangeMessagingBridge(CHANGE_STREAM), MongoCsfleClientFactory(CSFLE), MongoQueryableEncryptionCollectionManager(QUERYABLE_ENCRYPTION), MongoGridFsMigrationJob(GRIDFS_COMPATIBILITY), MongoShardingAdminGateway(SHARDING), MongoTenantClientRegistry·MongoTenantMigrationCoordinator(DATABASE_PER_TENANT).
  • @MongoAdvancedPolicy 11개.
  • 어느 쪽도 아닌 구체 클래스 1개: MongoAdvancedConfiguration.

MongoChangeMessagingBridge 참조 위치

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

그 하나가 누락이 아닌 이유

MongoAdvancedRules.concreteClass()@Configuration을 명시적으로 제외하며 이유를 적는다: "A @Configuration class is the package's composition root: it builds entry points through the guard rather than being one, and gating it would gate the thing that supplies the guard." interface·enum·record·익명·private 중첩·abstract도 같은 방식으로 제외되고 각각 근거가 붙어 있다. 즉 §83이 말하는 불변식은 문서가 아니라 코드로 서 있다. 이 leaf에서 "문서가 주장하고 코드가 지키지 않는다"를 여러 번 본 뒤라, 여기서는 그 반대가 성립한다는 것을 명시해 둘 가치가 있다.

던지기만 하는 메서드를 값으로 바꾼 두 수리

MongoTimeSeriesCapabilityValidator는 네 개의 던지기만 하는 메서드를 supportFor(capability) → MongoTimeSeriesSupport(지원 여부 + 이유)로 바꿨고, MongoQueryableEncryptionProfile은 세 개의 던지기만 하는 static factory를 supportFor(MongoQueryShape) → MongoQueryShapeSupport로 바꿨다. 근거도 동일하다 — "A factory that never returns is not an API: it cannot appear in working code, so its only reachable use is a test asserting that it throws, and the design-time question it was meant to answer is only answered by running it."