Kafka in the Wild
summary
Claims that reusing domain-defined Kafka topics cuts delivery time by eliminating duplicated, mutated datasets; shows a working design and demo using Kafka topics, Event Storming and schema-bound events to prevent a Kafka spiderweb. Explains metadata required (lineage, business owner, distribution), maps CQRS/DDD patterns into an Enterprise Domain Driven Design for a data mesh, and describes how producers publish consistent datasets so consumers get one authoritative source.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:29Agenda
- 2:35The problem
- 8:34History of data segregation within apps
- 10:22CQRS for operational systems
- 11:26DDD for a single application – Generic example
- 13:14DDD merged with event storming
- 13:58Eventing diagram
- 15:56Enterprise domain driven design
- 18:42Operational vs Data/Analytics ecosystems
- 20:23Monoliths vs Data mesh
- 24:45Summary
related talks
41mKafka as a Platform: The Ecosystem from the Ground Up
39mKafka as a Platform: The Ecosystem from the Ground Up
01h 00mKafka as a Platform: the Ecosystem from the Ground Up
41mKafka as a Platform: the Ecosystem from the Ground Up
01h 00mKafka as a Platform: the Ecosystem from the Ground Up
54mKafka as a Platform: the Ecosystem from the Ground Up
01h 00mIn Depth Kafka Streams
01h 07mKafka Streams and KSQLDB