Game of Streams: How to Tame & Get the Most from your Messaging Platforms
summary
Shows how Spring Cloud Stream plus binders for RabbitMQ and Kafka actually get wired: live-coded supplier → function → consumer beans that stream ADS‑B aircraft position Fluxes, transform to minimal payloads, and log them. Demonstrates consumer groups for competing‑consumer scaling, automatic partition handling, retry/resume on upstream failure, and switching binders at runtime with no code changes. Emphasizes concrete configs, Docker/local defaults, and when to use supplier/function/consumer vs legacy source/processor/sink.
AI-written summary · about
chapters (10)
- 0:00Introduction to messaging platforms
- 8:55Why use Spring Cloud Stream
- 12:29Setting up the demo project
- 28:54Building the source service
- 36:25Creating the processor service
- 37:47Developing the sync service
- 41:17Running the demo pipeline
- 43:46Switching from Rabbit to Kafka
- 46:43Accessing the source code
- 48:22Q&A session
related talks
57mGame of Streams: How to Tame and Get the Most from Your Messaging Platforms
43mEvent Streams & Data Rapids: Harnessing the Full Power of Messaging Platforms.
58mGame of Streams
51mSpring Cloud Stream: Developer Recipes, Tips and Tricks
01h 12mCloud Event Driven Architectures with Spring Cloud Stream 2.0
51mEvent Driven with Spring
48mSpring for Rabbit Super Stream and SQL filters
01h 17mMessage Driven Microservices in the Cloud