The Future of Event-driven Microservices with Spring Cloud Stream
summary
Argues that microservices need event log and CQRS and Event Sourcing to manage distributed state, shows a concrete architecture: Spring Boot command service writes ordered events to Apache Kafka, Spring Cloud Stream consumers build materialized views, API Gateway (Spring Cloud/Zuul) fronts query services. Demo creates a project and commits, an AWS Lambda updates a MongoDB view (a “t coupling” query) so file-pair counts update (example: six captures), and recommends Spring Cloud Function for serverless handlers.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:36The monolithic challenge
- 5:51Understanding microservices
- 9:02Architecture transitions
- 12:31Drivers for event-driven design
- 14:59Event-driven principles
- 25:07Implementing CQRS and serverless
- 29:10Live demo and closing
related talks
37mBeyond Microservices: Streams, State & Scalability
01h 12mCloud Event Driven Architectures with Spring Cloud Stream 2.0
47mData Microservices with Spring Cloud
52mCloud-native streaming and event-driven microservices
58mImplementing Event-driven Microservices
01h 25mBuilding microservices with event sourcing and CQRS
42mCreating event-driven microservices: the why, how and what
17m7 Reasons why your microservices should use Event Sourcing & CQRS
