ddd4j MQ

Overview

All broker adapters unify onto MQClient, MQListener, MQEvent, and Acknowledgment; choose delivery and operational semantics first, then the broker.

When to Use

• Selecting a broker against delivery semantics: Kafka, RabbitMQ, Pulsar/TDMQ, RocketMQ/ONS, ActiveMQ/Artemis, MQTT, NATS, SQS, Redis Stream, or in-process Disruptor.
• Implementing producers/consumers on the unified MQClient, MQListener, MQEvent, and Acknowledgment API.
• Designing ACK/NACK policy: ack after successful business processing, requeue or dead-letter on failure.
• Configuring retries with backoff, an upper bound, and dead-lettering.
• Handling listener lifecycle: required listeners blocking startup on failure, partial-failure rollback, idempotent close.
• Verifying real publish→consume→ack round-trips with Testcontainers.

When NOT to Use

Do not use this skill when: