This tutorial shows how to configure Spring Cloud Stream's RabbitMQ binder to requeue failed messages, provides a complete Java example with producer and consumer code, explains the difference from default retry, and demonstrates using a dead‑letter queue to prevent message buildup.
This article explains Spring Cloud Stream’s default retry mechanism, demonstrates a complete example of producing and consuming messages with intentional failures, shows how to configure retry attempts, and discusses what happens when retries succeed or ultimately fail, providing practical guidance for reliable message processing.
This guide explains why using identical @Input and @Output channel names in Spring Cloud Stream causes bean definition conflicts, and shows how to rename channels and configure them to share the same destination topic so a microservice can safely produce and consume its own messages.
This article explains why duplicate message consumption occurs when using Spring Cloud Stream with RabbitMQ or Kafka, introduces the concept of consumer groups, and provides a step‑by‑step Java example showing how to configure and use consumer groups to ensure each message is processed by only one instance.
