16 implemented chapters3 system tracks16 bounded endpoint families

Java → JVM → Spring → PostgreSQL

외울 목록이 아니라, 한 요청을 설명할 수 있는 시스템으로.

추천 순서는 있지만 모든 구현 chapter는 처음부터 열려 있습니다. 각 화면은 prediction → bounded run → captured replay → closed-book transfer를 요구하며, 완료 표시는 이 브라우저의 학습 marker일 뿐 자격증이나 이해의 증명이 아닙니다.

추천 시작점 열기

TRACK 01 · 5 chapters

Java Foundations

  1. J00~45 min

    Reference, object, and method boundaries

    Trace one small Java program from source to a real bounded Java 21 child-process receipt.

    CAPTUREDJLS_CONTRACTJVMS_CONTRACTDEPLOYMENT_CONTRACTBUILD_CONTRACTCONCEPTUAL_MODELDERIVEDNOT_OBSERVED
    chapter 열기
  2. J01~? min

    Values & flow

    값은 statement와 method 경계를 지나며 언제 바뀌고, 언제 그대로 남는가?

    CAPTUREDJLS_CONTRACTJVMS_CONTRACTBUILD_CONTRACTDEPLOYMENT_CONTRACTCONCEPTUAL_MODELDERIVEDNOT_OBSERVED
    chapter 열기
  3. J02~? min

    Equality & hash

    같은 reference와 같은 logical value는 어떻게 다르고, hash collection은 어떤 계약을 신뢰하는가?

    CAPTUREDJLS_CONTRACTJVMS_CONTRACTBUILD_CONTRACTDEPLOYMENT_CONTRACTCONCEPTUAL_MODELDERIVEDNOT_OBSERVED
    chapter 열기
  4. J03~? min

    Polymorphism

    compile-time type와 runtime object type은 method 선택과 안전성에 각각 어떤 역할을 하는가?

    CAPTUREDJLS_CONTRACTJVMS_CONTRACTBUILD_CONTRACTDEPLOYMENT_CONTRACTCONCEPTUAL_MODELDERIVEDNOT_OBSERVED
    chapter 열기
  5. J04~? min

    Generics & collections

    element type와 access pattern을 어떤 compile-time 계약과 collection 구조로 표현할 것인가?

    CAPTUREDJLS_CONTRACTJVMS_CONTRACTBUILD_CONTRACTDEPLOYMENT_CONTRACTCONCEPTUAL_MODELDERIVEDNOT_OBSERVED
    chapter 열기

TRACK 02 · 4 chapters

JVM & Concurrency

  1. J05~? min

    Exceptions & resources

    실패가 call stack과 resource owner를 지나갈 때 무엇을 보존해야 하는가?

    CAPTUREDJLS_CONTRACTBUILD_CONTRACTNOT_OBSERVED
    chapter 열기
  2. J06~? min

    Classloading & bytecode

    source·build artifact·runtime class identity를 어디까지 실제로 확인했는가?

    CAPTUREDBUILD_CONTRACTJVMS_CONTRACTNOT_OBSERVED
    chapter 열기
  3. J07~? min

    Heap & GC evidence

    reachable·retained·collected 중 이번 run이 실제로 말할 수 있는 범위는?

    CAPTUREDDERIVEDNOT_OBSERVED
    chapter 열기
  4. J08~? min

    Threads & the JMM

    thread 사이의 순서·visibility·atomicity·lifecycle을 어떤 coordination으로 증명하는가?

    CAPTUREDJMM_CONTRACTNOT_OBSERVED
    chapter 열기

TRACK 03 · 7 chapters

Spring request to database

  1. S00~45 min

    Browser to PostgreSQL: the whole request

    Build the ownership map first, then replay one captured request without pretending it is a live distributed trace.

    CAPTURED_REQUEST_RECEIPTDERIVED_TOPOLOGYNOT_OBSERVED
    chapter 열기
  2. S01~45 min

    Move work across controller, service, and database

    Edit one reviewed work-placement patch, predict its cost, run it, and compare immutable receipts.

    REAL_HIBERNATE_POSTGRESQLCAPTURED_RECEIPTNOT_OBSERVED
    chapter 열기
  3. S02~50 min

    From plain object ownership to a Spring proxy

    Compare direct construction with container wiring and observe the transaction consequence of the ownership change.

    REAL_SPRING_CONTEXTREAL_POSTGRESQL_STATENOT_OBSERVED
    chapter 열기
  4. S03~60 min

    Definition, resolution, scope, lifecycle, and backoff

    Run six reviewed container scenarios in isolated ApplicationContexts and defend the refresh decisions.

    REAL_ISOLATED_APPLICATION_CONTEXTCAPTURED_LIFECYCLENOT_OBSERVED
    chapter 열기
  5. S04~90 min

    MVC boundary and outbound resilience

    Trace the inbound Spring MVC boundary, then compare timeout, retry, idempotency, and saturation policies against a bounded loopback fault source.

    ACTUAL_SPRING_MVC_EVENTSREAL_EPHEMERAL_LOOPBACK_HTTPBOUNDED_CLIENT_EXECUTORHTTP_RESPONSENOT_OBSERVED
    chapter 열기
  6. S05~120 min

    Repository shape, transaction boundary, and connection lifetime

    Complete three independent PostgreSQL missions: query shape, proxy-owned transaction boundaries, and the connection/lock lifetime created by slow work placement.

    REAL_HIBERNATE_POSTGRESQLREAL_HIKARI_POSTGRESQLPOST_FAILURE_ROWSPG_BLOCKING_PIDSNOT_OBSERVED
    chapter 열기
  7. S06~120 min

    JVM scope, capacity, invariant, and wait-for cycle

    Connect one-JVM JMM repairs to the database ownership boundary, then separate Hikari pressure, lost-update correctness, and PostgreSQL deadlock mechanics.

    REAL_JAVA_21_WORKERSJMM_CONTRACTREAL_HIKARI_POSTGRESQLREAL_TRANSACTION_INTERLEAVINGNOT_OBSERVED
    chapter 열기

Explicitly not in this release

Spring async/Kafka/cache, live distributed tracing, arbitrary Java execution, 그리고 실제 learner comprehension evidence는 아직 이 registry에 포함하지 않습니다.