Reacting to an Event-Driven World
summary
Claim: Kafka plus nonreactive code is not enough; achieving end-to-end reactivity requires the four reactive manifesto behaviors: message-driven, elasticity and resiliency, and responsiveness. Concrete choices: run a Kafka cluster with at least three brokers and use a replication factor of three; size partitions to match consumer groups (demo uses a topic with three partitions and consumer groups of three). Built a barista app and UI using the Vert.x Kafka client to show offsets and partitions; switching from the plain Java client to Vert.x simplifies pause/resume and makes the flow work reliably.
AI-written summary · about
chapters (14)
- 0:00Intro
- 3:28Welcome
- 3:54Slides
- 4:11Coffee
- 7:51Kafka
- 9:57Apache Kafka
- 14:28Reactive Architecture Patterns
- 15:59Reactive Programming
- 17:21Kafka Configuration
- 18:03Kafka Resiliency
- 24:49Kafka Elasticity
- 28:59Writing an Application
- 32:00Vertex Application
- 37:10Summary
