Lesson 01
Event-Driven Architecture Decisions Explained
Decision: choose asynchronous boundaries from durable facts, ownership, delay, duplicates, ordering, and recovery.
Event-Driven Systems topic cluster
A production learning path for event architecture, Kafka, contracts, reliable publication, duplicate-safe consumption, ordering, recovery, and operations.
17 ordered lessons ยท Interactive failure lab
Move from architecture and contracts through publication, consumption, convergence, coordination, production operations, and deterministic crash experiments.
Lesson 01
Decision: choose asynchronous boundaries from durable facts, ownership, delay, duplicates, ordering, and recovery.
Lesson 02
Decision: separate broker delivery from application processing and business completion.
Lesson 03
Decision: align partition keys, group parallelism, offsets, and ordering with business invariants.
Lesson 04
Decision: place acknowledgment after the durable effect while planning for redelivery.
Lesson 05
Decision: separate event envelopes, payload schemas, channels, operations, and transport bindings.
Lesson 06
Decision: test structural and semantic compatibility across retained events and supported consumers.
Lesson 07
Decision: commit business state and publication intent atomically inside one local database.
Lesson 08
Decision: operate recoverable claims, broker acceptance, stable identity, and reconciliation.
Lesson 09
Decision: commit duplicate detection with the business update under a uniqueness invariant.
Lesson 10
Decision: match ACK, retry, DLT, and transaction settings to the actual durable effect.
Lesson 11
Decision: stop bounded automatic work and make remediation and replay an operated state.
Lesson 12
Decision: combine stable event identity with entity versions and atomic conditional updates.
Lesson 13
Decision: persist long-running transitions, compensation, and manual intervention.
Lesson 14
Decision: bound worker admission, retry, expiry, duplicate safety, and operational ownership.
Lesson 15
Decision: accept signed delivery, respond deliberately, and process downstream work safely.
Lesson 16
Decision: trace user impact through producer, broker, consumer, retry, and business evidence.
Lesson 17
Interactive failure lab: predict loss, replay, duplicate effects, idempotent convergence, and retry exhaustion from a deterministic timeline.