Outline: (1) why event-driven: the synchronous chain vs publishing an event; (2) core concepts; (3) Kafka: the log, keys and ordering, durability; (4) messaging patterns: pub/sub, competing consumers, event sourcing, CQRS; (5) delivery guarantees and idempotent consumers; (6) outbox and sagas; (7) dead letter queue; (8) when to use it, and the pitfalls.
Let the class answer before showing the bullets. The alternative contract: publish an event and let interested parties react asynchronously.
The page's queue-depth simulation: producer 3/step, consumer 2/step → the queue grows without bound; the consumer scales to 5/step at step 10 → it catches up. That backlog is the consumer lag.