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>
54 lines
2.4 KiB
Markdown
54 lines
2.4 KiB
Markdown
---
|
|
kind: CONCEPT
|
|
slug: messaging-policy-c02
|
|
title: bean 정의는 전부 starter 쪽에 있다
|
|
topic: delivery-and-settlement-models
|
|
project: clean-architecture-backend-template
|
|
status: 게시 전
|
|
sourceRevision: 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916
|
|
rootTreeNode: concept:messaging-policy-c02
|
|
evidenceCapturedOn: 2026-09-01
|
|
assets:
|
|
- key: messaging-policy-c02
|
|
file: ../../../final/evidence/rendered/messaging-policy-c02.svg
|
|
evidence:
|
|
- ../../../final/evidence/raw/messaging-policy-c02.txt
|
|
source:
|
|
- 원본 분석 절은 analysis/messaging/messaging-policy.md#L84 이다.
|
|
module: messaging-policy
|
|
---
|
|
|
|
# bean 정의는 전부 starter 쪽에 있다
|
|
|
|
들어오는 것: messaging-core-api(api), messaging-schema-api(api). 둘 다 api인 이유는 DestinationProfile이 DeliveryGuarantee·OrderingScope·DestinationKind·DestinationName(core-api)와 SchemaCompatibility(schema-api)를 필드로 갖기 때문이다.
|
|
|
|
## 관계
|
|
|
|
- **구성 오류는 한 예외 타입과 안정 코드로 보고한다**
|
|
같은 분석 리프에서 끌어낸 규칙이다.
|
|
- **저장소 밖 문서를 절 번호로 인용하지 않는다**
|
|
같은 분석 리프에서 끌어낸 규칙이다.
|
|
- **부팅 경로의 알고리즘 복잡도는 문서화한다**
|
|
같은 분석 리프에서 끌어낸 규칙이다.
|
|
|
|
## 본문
|
|
|
|
<!-- body:start -->
|
|
|
|
들어오는 것은 `messaging-core-api`(api)와 `messaging-schema-api`(api)다. 둘 다 `api`인 이유는 `DestinationProfile`이 `DeliveryGuarantee`·`OrderingScope`·`DestinationKind`·`DestinationName`(core-api)와 `SchemaCompatibility`(schema-api)를 필드로 갖기 때문이다.
|
|
|
|
## 이 기록이 다루는 범위
|
|
|
|
:::evidence key="messaging-policy-c02" alt="코드베이스에서 파일 목록을 만든 출력 25줄. 이 기록이 다루는 범위가 그 목록이다." caption="코드베이스 파일 목록 — 25줄 · exit 0" zoom="true"
|
|
:::
|
|
|
|
## 나가는 쪽
|
|
|
|
`messaging-transport-spi`, `messaging-runtime-core`, `messaging-kafka`, `messaging-kafka-share-experimental`, `messaging-rabbit`, `messaging-outbox-jdbc-postgresql`, `messaging-admin-api`, `messaging-admin-runtime`, `messaging-pulsar-experimental`, `messaging-nats-experimental`, `messaging-spring-cloud-stream-bridge`, `messaging-spring-boot-starter`, `messaging-testkit`.
|
|
|
|
## 실제 배선 지점 넷이 전부 starter 안에 있다
|
|
|
|
전부 `messaging-spring-boot-starter/MessagingCoreAutoConfiguration`이다. 이 leaf 자체는 Spring 주석을 갖지 않는다.
|
|
|
|
<!-- body:end -->
|