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>
2.0 KiB
2.0 KiB
kind, slug, title, topic, project, status, sourceRevision, rootTreeNode, evidenceCapturedOn, assets, evidence, source, module
| kind | slug | title | topic | project | status | sourceRevision | rootTreeNode | evidenceCapturedOn | assets | evidence | source | module | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CONCEPT | messaging-outbox-jdbc-postgresql-c04 | 쓰기와 배출과 정리와 저널이 각각 다른 경로다 | transaction-and-consistency-models | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:messaging-outbox-jdbc-postgresql-c04 | 2026-09-01 |
|
|
|
messaging-outbox-jdbc-postgresql |
쓰기와 배출과 정리와 저널이 각각 다른 경로다
네 실행 경로가 있고 각각 진입점과 종료 조건이 다르다.
본문
네 실행 경로가 있고 각각 진입점과 종료 조건이 다르다.
쓰기 — 비즈니스 트랜잭션 → append(record) → 트랜잭션 3중 검사 → DataSourceUtils.getConnection → INSERT(22컬럼).
배출 — MessagingOutboxRelayLifecycle → worker.start() → runPass() → relay.runOnce(now) → 청구/발행/종결 → scheduler.backoff(unproductive) → 다음 패스 자기 스케줄링.
DataSourceUtils 참조 위치
:::evidence key="messaging-outbox-jdbc-postgresql-c04" alt="코드베이스에서 DataSourceUtils 를 검색한 출력 15줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="DataSourceUtils 코드베이스 검색 — 15줄 · exit 0" zoom="true" :::
정리와 admin 저널
정리 — OutboxCleanupJob.runOnce(now) → cutoff = now - retention → purgePublishedBefore(cutoff) 무제한 오버로드 ×(최대 maxBatches, 실제로는 2회) → §12.1(a).
admin 저널 — begin → INSERT ON CONFLICT / TAKE_OVER → checkpoint × N → complete 또는 fail.