Spring Cloud Stream Past, Present and Future
summary
Spring Cloud Stream shifts from runtime annotations to a Spring Cloud Function model: code is written as Supplier/Function/Consumer and stream listener removed so binders (Kafka, Rabbit, Pulsar) attach via dependencies. Demo shows a Foo function echoing strings, RabbitMQ queues auto provision destination on startup, and composing functions as Foo|Bar with binding name mapping. Message headers arrive via a BiFunction signature (payload, Map), functional error handling routes failed messages to an error consumer after 3 retries, and a Pulsar binder demo converts User → RegisteredUser using native encoding.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:04Framework concepts
- 4:41Evolution of the programming model
- 8:09Spring Cloud function integration
- 12:04Hands-on coding demo
- 18:45Function composition and configuration
- 26:01Advanced message handling
- 32:32Error handling and routing
- 39:43Apache Pulsar binder demo
- 49:06Future directions
related talks
51mEvent Driven with Spring
45mSweet Streams (Are Made of This)
52mCloud-native streaming and event-driven microservices
46mSpring Cloud Stream - a new Rick and Morty adventure
55mSpring, Functions, Serverless and You
39mIntroducing Spring for Apache Pulsar
52mStream Processing with the Spring Framework Like You’ve Never Seen It Before
53mSpring and Messaging: The next development generation