ddd4j-boot MQ

Overview

Covers Kafka, RabbitMQ, Pulsar, RocketMQ, ActiveMQ, MQTT, NATS, SQS, ONS/TDMQ, and listener lifecycle uniformly, not split per artifact. Before use, confirm the maintenance line through ddd4j-boot-version-selection.

When to Use

• Choosing a broker adapter (Kafka, RabbitMQ, Pulsar, RocketMQ, ActiveMQ, MQTT, NATS, SQS, ONS/TDMQ) for a ddd4j-boot service, matched to delivery semantics and ordering needs.
• Wiring the MQ auto-configuration, listener registrar, and topic/tag/group/namespace settings on a specific Boot line (2.3–4.1).
• Deciding required versus optional listeners — whether a broker being down must block startup or degrade gracefully.
• Configuring acknowledgment, retry, and dead-letter policy, and verifying duplicates and recovery behavior.
• Auditing shutdown: producer/listener close must be idempotent, with an explicit resource owner and rollback.
• Diagnosing messaging failures: beans assembled but nothing consumed, listeners silently absent, or retries looping without reaching the dead letter.

When NOT to Use

Do not use this skill when: