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>
56 lines
2.8 KiB
Markdown
56 lines
2.8 KiB
Markdown
---
|
|
kind: CONCEPT
|
|
slug: messaging-spring-cloud-stream-bridge-c04
|
|
title: send가 true를 반환해도 AMBIGUOUS다
|
|
topic: delivery-and-settlement-models
|
|
project: clean-architecture-backend-template
|
|
status: 게시 전
|
|
sourceRevision: 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916
|
|
rootTreeNode: concept:messaging-spring-cloud-stream-bridge-c04
|
|
evidenceCapturedOn: 2026-09-01
|
|
assets:
|
|
- key: messaging-spring-cloud-stream-bridge-c04
|
|
file: ../../../final/evidence/rendered/messaging-spring-cloud-stream-bridge-c04.svg
|
|
evidence:
|
|
- ../../../final/evidence/raw/messaging-spring-cloud-stream-bridge-c04.txt
|
|
source:
|
|
- 원본 분석 절은 analysis/messaging/messaging-spring-cloud-stream-bridge.md#L309 이다.
|
|
module: messaging-spring-cloud-stream-bridge
|
|
---
|
|
|
|
# send가 true를 반환해도 AMBIGUOUS다
|
|
|
|
검증: validator.validate(profile, bindingName, extendedProperties, enabled) → guard 4검사 → 이름 → 속성 8개 → production → BindingCapabilityReport.bridged(...) 발행: bridge.bindPublisher(dest, binding) → bridge.publish(dest, payload, headers) → send.send(...) → true면 AMBIGUOUS, false면 REJECTED 수신: consumerBridge.register(dest, binding, handler) → 바인더가 dispatch(binding, payload, headers) → handler.handle(...) (예외 그대로 전파)
|
|
|
|
## 관계
|
|
|
|
- **허용 의존 목록은 상한이므로 미사용을 잡지 않는다**
|
|
같은 분석 리프에서 끌어낸 규칙이다.
|
|
- **등록을 받는 컴포넌트는 해제도 제공한다**
|
|
같은 분석 리프에서 끌어낸 규칙이다.
|
|
- **함께 읽히는 두 맵은 한 값으로 묶는다**
|
|
같은 분석 리프에서 끌어낸 규칙이다.
|
|
- **에러 메시지가 지시하는 설정은 그 설정을 읽는 코드와 함께 존재해야 한다**
|
|
같은 분석 리프에서 끌어낸 규칙이다.
|
|
- **한 개념의 등록 상태를 두 객체가 나눠 갖지 않는다**
|
|
같은 분석 리프에서 끌어낸 규칙이다.
|
|
|
|
## 본문
|
|
|
|
<!-- body:start -->
|
|
|
|
세 경로가 있다.
|
|
|
|
**검증:** `validator.validate(profile, bindingName, extendedProperties, enabled)` → guard 4검사 → 이름 → 속성 8개 → production → `BindingCapabilityReport.bridged(...)`
|
|
|
|
**발행:** `bridge.bindPublisher(dest, binding)` → `bridge.publish(dest, payload, headers)` → `send.send(...)` → true면 `AMBIGUOUS`, false면 `REJECTED`
|
|
|
|
**수신:** `consumerBridge.register(dest, binding, handler)` → 바인더가 `dispatch(binding, payload, headers)` → `handler.handle(...)` (예외 그대로 전파)
|
|
|
|
## 이 기록이 다루는 범위
|
|
|
|
:::evidence key="messaging-spring-cloud-stream-bridge-c04" alt="코드베이스에서 파일 목록을 만든 출력 6줄. 이 기록이 다루는 범위가 그 목록이다." caption="코드베이스 파일 목록 — 6줄 · exit 0" zoom="true"
|
|
:::
|
|
|
|
<!-- body:end -->
|