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>
52 lines
2.5 KiB
Markdown
52 lines
2.5 KiB
Markdown
---
|
|
kind: CONCEPT
|
|
slug: messaging-pulsar-experimental-c01
|
|
title: 알 수 없는 실패의 기본값을 모호로 둔다
|
|
topic: result-and-failure-algebra
|
|
project: clean-architecture-backend-template
|
|
status: 게시 전
|
|
sourceRevision: 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916
|
|
rootTreeNode: concept:messaging-pulsar-experimental-c01
|
|
evidenceCapturedOn: 2026-09-01
|
|
assets:
|
|
- key: messaging-pulsar-experimental-c01
|
|
file: ../../../final/evidence/rendered/messaging-pulsar-experimental-c01.svg
|
|
- key: messaging-pulsar-experimental-c01-diagram
|
|
file: ../../../final/assets/diagrams/messaging-pulsar-experimental-c01.svg
|
|
evidence:
|
|
- ../../../final/evidence/raw/messaging-pulsar-experimental-c01.txt
|
|
source:
|
|
- 원본 분석 절은 analysis/messaging/messaging-pulsar-experimental.md#L50 이다.
|
|
module: messaging-pulsar-experimental
|
|
---
|
|
|
|
# 알 수 없는 실패의 기본값을 모호로 둔다
|
|
|
|
분류는 타입 있는 신호만 본다. `PulsarPreSendRejection`이면 REJECTED, `TimeoutException`이면 시간 초과, 나머지는 전부 AMBIGUOUS다. javadoc이 이전 구현과 그 결함을 적는다.
|
|
|
|
## 본문
|
|
|
|
<!-- body:start -->
|
|
|
|
javadoc 이 이전 구현과 그 결함을 적는다. 예전에는 예외의 클래스 단순 이름을 읽어서 `"Timeout"`이면 모호, 그 밖이면 거절로 분류했다.
|
|
|
|
> "Classification used to read the exception's class simple name: `"Timeout"` meant ambiguous, anything else meant rejected. A class name is not part of Pulsar's contract — it changes between client versions — and defaulting the unknown case to `REJECTED` tells the caller nothing was transmitted, which is how the same entry is published to the bookies twice."
|
|
|
|
기본값이 모호로 바뀐 것이 핵심이다. 알 수 없는 실패에서 안전한 방향은 모호다.
|
|
|
|
## 분류가 갈라지는 자리
|
|
|
|
:::evidence key="messaging-pulsar-experimental-c01-diagram" alt="사전 거절과 그 밖의 실패가 나란히 놓이고 모호가 아래에 놓인 구조" caption="분류의 기본값" zoom="false"
|
|
:::
|
|
|
|
## 성공을 영수증이 아니라 복제 증거로 적는다
|
|
|
|
확인된 성공은 복제 증거로 기록된다 — 전송 미래가 설정된 수의 저장 노드에 기록된 뒤에야 해소되므로 영수증이 아니라 복제 증거다.
|
|
|
|
## 이 기록이 다루는 파일 범위
|
|
|
|
:::evidence key="messaging-pulsar-experimental-c01" alt="코드베이스에서 파일 목록을 만든 출력 8줄. 이 기록이 다루는 범위가 그 목록이다." caption="코드베이스 파일 목록 — 8줄 · exit 0" zoom="true"
|
|
:::
|
|
|
|
<!-- body:end -->
|