Creating event-driven microservices: the why, how and what
summary
Explains how an event backbone replaces chatty REST chains by using Apache Kafka as the source of truth, demonstrating compaction to represent DB rows, change data capture via Kafka Connect/Debezium to stream existing databases, and consumer groups plus partition keys to preserve per-order ordering and scale event sourcing. Covers sagas for distributed transactions, CQRS for read-optimized views, and Kafka Streams for inline enrichment, notes production topology needs three or more brokers and careful handling of eventual consistency.
AI-written summary · about
chapters (15)
- 0:00Introduction to Kafka
- 1:32The problem with monoliths
- 3:37Event-centric architecture
- 6:58Event backbone overview
- 8:36Messaging vs streaming
- 11:32Shipping example scenario
- 16:14Database per service pattern
- 18:25Implementing sagas
- 22:02Event sourcing principles
- 25:12CQRS explained
- 27:28Kafka features
- 30:02Compaction and CDC
- 32:47Scalable consumption
- 36:41Kafka streams and closing
- 40:09Q&A session
related talks
33mMicroservices, Events, and Breaking the Data Monolith with Kafka
58mImplementing Event-driven Microservices
27mOptimize Your API with Event-Driven Microservice Architecture.
47mEvent-Driven Microservices = Microservices Done Right
51mPatterns & Practices of Implementing Event-driven MicroSvc...
31mDemystifying Event-Driven Architectures
37mBeyond Microservices: Streams, State & Scalability
17mOvercome By Events - Apache Kafka And Event-oriented Architecture
