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>
31 lines
1.2 KiB
Plaintext
31 lines
1.2 KiB
Plaintext
# 애플리케이션이 준 정책을 넣고, 그 정책이 불리는지 센다
|
|
AtomicInteger workCalls = new AtomicInteger();
|
|
|
|
JpaRetryPolicy customPolicy =
|
|
(failure, attempt) -> {
|
|
policyCalls.incrementAndGet();
|
|
return RetryDecision.fail("application policy says do not retry");
|
|
};
|
|
|
|
var profile =
|
|
TransactionProfile.write("order.write", Duration.ofSeconds(5))
|
|
.withRetryProfile(RetryProfile.boundedContention("order.write", 2));
|
|
|
|
|
|
애플리케이션 정책 호출 : 0
|
|
작업 호출 : 2
|
|
최종 예외 : SerializationFailureException
|
|
|
|
# 플랫폼이 자기 빈에 넣는 기본 프로파일
|
|
@ConditionalOnMissingBean
|
|
@ConditionalOnBean(SpringJpaTransactionExecutor.class)
|
|
public FullTransactionRetryCoordinator jpaRetryCoordinator(
|
|
SpringJpaTransactionExecutor executor, RetryEventListener retryListener, Clock clock) {
|
|
return new JpaTransactionAutoConfiguration(clock)
|
|
.retryCoordinator(
|
|
executor,
|
|
dev.caskeleton.adapter.outbound.persistence.api.transaction.RetryProfile
|
|
.boundedContention("jpa-platform-default", 3),
|
|
retryListener);
|
|
}
|