Event-Driven Architecture and Streaming Foundations

TRACK

Application-level event-driven design: event boundaries, broker models, delivery semantics, contracts, idempotency, replay, backpressure, and operational review. This track is the bridge into deeper messaging internals, stream processing, CDC, and distributed workflow tracks.

How do I reason about application-level event-driven design: event boundaries, broker models, delivery semantics, contracts, idempotency, replay, backpressure, and operational review. This track is the bridge into deeper messaging internals, stream processing, CDC, and distributed workflow tracks?

16 lessons

Continues to Data Integration, CDC, and Pipelines/ Distributed Messaging and Queue Internals/ Distributed Transactions and Sagas/ Streaming Data Infrastructure/ Workflow Orchestration and Business Process Systems

LESSONS

001

Event-Driven Architecture Mental Model

[TODO]
002

Events, Commands, Messages, and Domain Facts

[TODO]
003

Producers, Consumers, Brokers, and Event Logs

[TODO]
004

Event Boundaries, Ownership, and Publication Responsibility

[TODO]
005

Queues, Topics, Pub/Sub, and Log Topologies

[TODO]
006

Routing, Fanout, and Subscriber Independence

[TODO]
007

Ordering, Partitioning, and Idempotency Boundaries

[TODO]
008

Delivery Semantics and Retry Discipline REVIEW

[TODO]
009

Choreography, Orchestration, and Process Visibility

[TODO]
010

Event Sourcing, CQRS, and Projection Boundaries

[TODO]
011

Outbox, Inbox, and Dual-Write Avoidance

[TODO]
012

Schema Evolution and Consumer Compatibility

[TODO]
013

Replay, Backfills, DLQs, and Poison Events

[TODO]
014

Backpressure, Lag, and Operational Signals

[TODO]
015

Event-Driven Architecture Review Check REVIEW

[TODO]
016

Capstone: Design an Event-Driven Service Platform CAPSTONE

[TODO]

← Back to Distributed Systems