PREVIEW: Event-Driven Services with Stateful Streams
summary
Makes the concrete claim that you can build stateful, request‑response capable services on top of stream processing rather than separate databases, using Kafka Streams and Confluent tooling to stitch data islands into an event‑sourced joined‑up view. Walks through patterns—orders, stock, basket services with per‑service databases—shows receiver-driven flow control to avoid tight point‑to‑point coupling, and argues these patterns reduce coupling while enabling independent deployability and operational transparency.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:07Microservice are an evolution
- 0:34Apply the Single Responsibility Principal
- 2:14When it comes to data, microservices promote independence
- 3:2620. Microservices 30 - What's next?
- 3:52Loose Coupling • Data Enabled
- 4:18A measure of the assumptions two services make doout one another when they exchange information
- 4:47Leverage Receiver Driver Flow Control
related talks
23mEvent-Driven Architecture: Unleashing responsiveness
37mBeyond Microservices: Streams, State & Scalability
50mAddressing Recent Events
36mThe Future of Event-driven Microservices with Spring Cloud Stream
55mThe data dichotomy: Rethinking data and services with streams
42mCreating event-driven microservices: the why, how and what
47mStream All the Things!
27mKeynote II: Kafka and the Rise of Event-Driven Microservices