The Tales of Event-Driven Told by a Spring Developer
summary
Argues that treating domain changes as immutable events stored in a log simplifies microservice integration, using Apache Kafka as the event store, Kafka Streams for replicated local state stores, and a connector to stream legacy DB changes into topics. Shows a Rotten Tomatoes–style refactor where write-to-db plus publish-to-log becomes durable source-of-truth, services replay streams after outages, and local “transactions” are autonomous rather than ACID. Demo uses Kotlin and Spring Boot tooling.
AI-written summary · about
chapters (5)
related talks
40mEvent Streaming Applications with Kafka Streams, Spring Kafka and Actuator
44mThe Changing Face of ETL: Event-Driven Architectures for Data Engineers
50mApplication development and data in the emerging world ...
33mMicroservices, Events, and Breaking the Data Monolith with Kafka
48mIntegrating microservices by accepting the data dichotomy
55mDemystifying Stream Processing with Apache Kafka
26mKafka in the Wild
01h 00mIn Depth Kafka Streams