ddd4j-cloud Stream

Overview

Covers StreamBridge, function/binding/destination, ACK/NACK, Kafka, RabbitMQ, Pulsar, and RocketMQ uniformly, not split per artifact. Choose the Cloud→Boot→ddd4j primary combination first, then read the current branch.

When to Use

• Mapping functions, binding names, and physical destinations per broker (Kafka, RabbitMQ, Pulsar, RocketMQ).
• Publishing with StreamBridge and wiring consumer ACK/NACK with retry and dead-letter policy.
• Propagating Context/Tenant into message headers and restoring them on consume.
• Applying the line's BindingNamingContributor naming rules.
• Diagnosing messages that are never consumed, duplicated, or lost on redelivery.
• Verifying broker integration with real publish/consume, ack/nack/retry, duplicates, and recovery runs.

When NOT to Use

Do not use this skill when: