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
parent 43bccd08a8
commit b2963105a8
5017 changed files with 372751 additions and 4943 deletions
@@ -3,7 +3,8 @@ id: c1158754-e3d2-47b8-bb41-81787c0ca84b
 kind: CASE
 slug: collection-fetch-join-in-memory-paging
 title: Collection Fetch Join Pagination의 In-memory Paging
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/c1158754-e3d2-47b8-bb41-81787c0ca84b/edit"
@@ -3,7 +3,8 @@ id: 32d0be7d-d88e-4760-8d91-35d3a233a99a
 kind: CASE
 slug: eager-toone-nplus1-without-access
 title: Fetch 타입이 아니라 조회 방식이 만든 ToOne N+1
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/32d0be7d-d88e-4760-8d91-35d3a233a99a/edit"
@@ -3,7 +3,8 @@ id: 7ed75172-fd56-42bf-956a-8f9fc1cca235
 kind: CASE
 slug: fetch-join-multibag-and-row-explosion
 title: Fetch Join으로 N+1을 해결하다 만난 MultiBag과 행 폭증
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/7ed75172-fd56-42bf-956a-8f9fc1cca235/edit"
@@ -3,7 +3,8 @@ id: 4c9c3b90-bc89-4300-9334-088ea95d37d8
 kind: CASE
 slug: projection-row-over-fetch
 title: Projection 이후에도 1,509행을 읽은 Row Over-fetch
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/4c9c3b90-bc89-4300-9334-088ea95d37d8/edit"
@@ -3,7 +3,8 @@ id: e6715e81-6dbd-4287-8e19-946c334f38fb
 kind: CASE
 slug: visibility-or-breaks-keyset-index
 title: Visibility OR이 Keyset Index를 깨뜨린 문제
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/e6715e81-6dbd-4287-8e19-946c334f38fb/edit"
@@ -3,7 +3,8 @@ id: 08a74b35-10c3-4874-8fbc-209b0b6e942e
 kind: PROJECT_DECISION
 slug: batch-fetch-for-entity-graph
 title: Entity Graph 조회에는 Batch Fetch를 사용한다
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/08a74b35-10c3-4874-8fbc-209b0b6e942e/edit"
@@ -3,7 +3,8 @@ id: 7f248f68-ce2b-43ec-94ce-82324d0bd1a7
 kind: PROJECT_DECISION
 slug: keep-read-model-as-cqrs-lite
 title: 현재 Read Model은 CQRS-lite로 유지한다
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/7f248f68-ce2b-43ec-94ce-82324d0bd1a7/edit"
@@ -3,7 +3,8 @@ id: 1dbce381-f0dc-4d49-ad68-bd31d205677e
 kind: PROJECT_DECISION
 slug: keyset-for-feed-pagination
 title: Feed Pagination은 Keyset을 사용한다
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/1dbce381-f0dc-4d49-ad68-bd31d205677e/edit"
@@ -3,7 +3,8 @@ id: ae6c9bea-d3a3-46e1-bbd4-8d580d336394
 kind: PROJECT_DECISION
 slug: measure-plan-on-real-postgresql
 title: Query Plan은 실제 PostgreSQL에서 측정한다
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/ae6c9bea-d3a3-46e1-bbd4-8d580d336394/edit"
@@ -3,7 +3,8 @@ id: 5e4d033c-d6fe-4257-a4dc-1ade44473c72
 kind: PROJECT_DECISION
 slug: no-collection-fetch-join-with-pagination
 title: Collection Fetch Join과 Pagination을 같이 사용하지 않는다
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/5e4d033c-d6fe-4257-a4dc-1ade44473c72/edit"
@@ -3,7 +3,8 @@ id: 4e3200c8-eff5-4442-ae84-ae7b7fa92c8b
 kind: PROJECT_DECISION
 slug: query-strategy-behind-port
 title: Query Strategy는 FeedQueryPort 뒤에서 소유한다
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/4e3200c8-eff5-4442-ae84-ae7b7fa92c8b/edit"
@@ -3,7 +3,8 @@ id: 30a37f34-b406-4061-b924-e22e0be0c3bf
 kind: PROJECT_DECISION
 slug: read-projection-for-screen-query
 title: 화면 조회는 Read Projection을 사용한다
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/30a37f34-b406-4061-b924-e22e0be0c3bf/edit"
@@ -3,7 +3,8 @@ id: e1e0e2a0-c6b6-45bf-be42-f697ba5e2fff
 kind: QUESTION
 slug: cardinality-estimate-after-analyze
 title: ANALYZE 이후 Cardinality Estimate는 어떻게 달라지는가
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/e1e0e2a0-c6b6-45bf-be42-f697ba5e2fff/edit"
@@ -3,7 +3,8 @@ id: 6cbe963f-86f8-4df6-be5a-900712970d01
 kind: QUESTION
 slug: concurrency-stability
 title: 실제 동시 트래픽에서도 이 구조가 안정적인가
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/6cbe963f-86f8-4df6-be5a-900712970d01/edit"
@@ -3,7 +3,8 @@ id: 5159c415-232d-424a-970a-b0db52746767
 kind: QUESTION
 slug: isolate-round-trip-and-row-volume
 title: Round Trip과 Row Volume을 독립 측정할 것인가
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/5159c415-232d-424a-970a-b0db52746767/edit"
@@ -3,7 +3,8 @@ id: b099ca65-bf9f-4d61-814c-74722453fa3c
 kind: QUESTION
 slug: nullable-first-highlighted-at
 title: Highlight 없는 FeedItem을 허용할 것인가
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/b099ca65-bf9f-4d61-814c-74722453fa3c/edit"
@@ -3,7 +3,8 @@ id: 5088ce14-b096-41d3-abba-64b7afb48bb9
 kind: QUESTION
 slug: promote-feed-visible-to-cqrs
 title: feed_visible을 Production CQRS로 승격할 것인가
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/5088ce14-b096-41d3-abba-64b7afb48bb9/edit"
@@ -3,7 +3,8 @@ id: 635fcedd-d402-4297-bcf3-9fcdf4200d28
 kind: REFERENCE
 slug: feed-visibility-query-pattern
 title: Feed Visibility Query Pattern
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/635fcedd-d402-4297-bcf3-9fcdf4200d28/edit"
@@ -3,7 +3,8 @@ id: db99cbc5-9123-4599-b368-39ff3170e81d
 kind: REFERENCE
 slug: fetch-strategy-selection
 title: Fetch Join · Batch · Projection 선택 기준
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/db99cbc5-9123-4599-b368-39ff3170e81d/edit"
@@ -3,7 +3,8 @@ id: 51095f6e-2cc8-439c-8648-065033614215
 kind: REFERENCE
 slug: fetch-type-vs-fetch-strategy
 title: Fetch Type과 Fetch Strategy 구분
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/51095f6e-2cc8-439c-8648-065033614215/edit"
@@ -3,7 +3,8 @@ id: 06788903-3dfa-4f70-b159-f1224384fd0b
 kind: REFERENCE
 slug: keyset-pagination-design
 title: Keyset Pagination 설계 기준
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/06788903-3dfa-4f70-b159-f1224384fd0b/edit"
@@ -3,7 +3,8 @@ id: b0b55ac9-c0a3-4c01-ba84-0aa478923ace
 kind: REFERENCE
 slug: nplus1-quantitative-diagnosis
 title: JPA N+1 정량 진단 기준
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/b0b55ac9-c0a3-4c01-ba84-0aa478923ace/edit"
@@ -3,7 +3,8 @@ id: e8c2e9ea-cd87-46f8-9469-849dbd433d86
 kind: REFERENCE
 slug: postgresql-query-plan-measurement
 title: PostgreSQL Query Plan 측정 기준
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/e8c2e9ea-cd87-46f8-9469-849dbd433d86/edit"
@@ -3,7 +3,8 @@ id: bf5f2462-0e94-4723-bdc8-f7dd709b2dbb
 kind: REFERENCE
 slug: top-n-per-group-selection
 title: Top-N-per-group 선택 기준
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/bf5f2462-0e94-4723-bdc8-f7dd709b2dbb/edit"