Files
document-haness/docs/clean-architecture-backend-template/tech-log-studio/state-machines-and-ownership/concept/concept-grpc-spring-boot-starter-c02.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

47 lines
2.0 KiB
Markdown

---
kind: CONCEPT
slug: grpc-spring-boot-starter-c02
title: 한 번에 전부 모아 실패한다
topic: state-machines-and-ownership
project: clean-architecture-backend-template
status: 게시 전
sourceRevision: 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916
rootTreeNode: concept:grpc-spring-boot-starter-c02
evidenceCapturedOn: 2026-09-01
assets:
- key: grpc-spring-boot-starter-c02
file: ../../../final/evidence/rendered/grpc-spring-boot-starter-c02.svg
evidence:
- ../../../final/evidence/raw/grpc-spring-boot-starter-c02.txt
source:
- 원본 분석 절은 analysis/grpc/grpc-spring-boot-starter.md#L87 이다.
module: grpc-spring-boot-starter
---
# 한 번에 전부 모아 실패한다
시작 검증기가 다섯 갈래 규칙을 담고, 어긴 것을 하나씩 던지지 않고 한 번에 모아 실패한다 — "so a deployment learns the whole list in one restart."
## 본문
<!-- body:start -->
javadoc 이 선정 기준을 적고, 규칙이 다섯 갈래다.
- **전송·보안** — production 전송이 아니면 거부, 배포 환경에서 TLS 미사용·trust-all·반사 전체 공개 거부
- **실행기** — 큐 용량 1 미만(무제한) 거부, 풀 크기 양수 요구
- **메서드** — 단항인데 사용 가능한 마감이 0, 명시적 재시도가 멱등 프로파일과 모순, 멱등 키 필수인데 원장 비활성, Stable 범위 밖 RPC 종류
- **채널** — Stable 스킴 요구, 두 재시도 소유자가 동시에 in-process 재시도
- **고급 격리** — Stable 스타터가 advanced 의존을 끌면 위반
## 이 기록이 다루는 파일 범위
:::evidence key="grpc-spring-boot-starter-c02" alt="코드베이스에서 파일 목록을 만든 출력 4줄. 이 기록이 다루는 범위가 그 목록이다." caption="코드베이스 파일 목록 — 4줄 · exit 0" zoom="true"
:::
## 하나씩 던지지 않는 이유
그리고 한 번에 전부 모아 실패한다 — "so a deployment learns the whole list in one restart."
<!-- body:end -->