Data Microservices with Spring Cloud
summary
Explains how to build lightweight, data-centric microservices that pass payloads through a durable broker instead of direct REST calls, using Spring Cloud Stream’s binder abstraction to connect to Kafka or RabbitMQ and scale with consumer groups and partitioning; demonstrates composing simple one‑purpose services into pipelines, highlights tradeoffs — eventual consistency, broker ops cost — and shows a concrete architecture using event sourcing plus CQRS with snapshots to reconstruct state and limit replay time.
AI-written summary · about
chapters (14)
- 0:00Introduction to data microservices
- 1:11What are data microservices
- 3:38Why focus on data instead of apps
- 6:09Benefits and drawbacks of data microservices
- 10:28Spring Cloud Stream overview
- 11:31Spring Cloud Stream architecture
- 16:13Scaling with consumer groups
- 18:18Partitioning for performance
- 21:50Data consistency challenges
- 29:47Event-driven alternatives to transactions
- 31:56Event sourcing pattern explained
- 35:32CQRS for read/write separation
- 39:06Summary and key takeaways
- 41:37Q&A session
related talks
36mThe Future of Event-driven Microservices with Spring Cloud Stream
01h 12mCloud Event Driven Architectures with Spring Cloud Stream 2.0
44mData Processing With Microservices
33mMicroservices, Events, and Breaking the Data Monolith with Kafka
01h 17mMessage Driven Microservices in the Cloud
28mPractical Microservices, Practical Whiskey
52mCloud-native streaming and event-driven microservices
51mSpring Cloud Stream: Developer Recipes, Tips and Tricks
