Learning path

The shortest useful route depends on what you must build or operate.

Application developer

Start with getting started to create one durable repository. Then read the audit model to distinguish snapshots from application rows and shadows from live entities. Finish with DDD and CQRS: you will see the exact persistence, audit, publication, and projection order and the gaps a production outbox must close.

Persistence integrator

Read repository map, then persistence selection. The Exposed page teaches schema and transaction ownership; the Redis page separates Lettuce and Redisson; the Kafka page makes the write-only contract explicit. Finish with failure contracts to define retry and reconciliation before wiring two destinations.

Operator or test engineer

Begin with observability to identify commit failures, query cost, Kafka lag, and projection drift. Testing then maps those risks to unit, database, and Testcontainers checks. The example’s OrderProjectionFlowTest is the executable end-to-end reference.

For background facilities, continue to the published Projects manual and Exposed manual. Their generic repository, transaction, Redis, Kafka, and Testcontainers contracts are intentionally not duplicated here.