Skip to content
EN FR

RabbitMQ Adapter

Documentation status: architecture — see Maturity and evidence.

Purpose

RabbitMQ can be used as an external message broker behind the logiCells messaging boundary. The adapter connects published or application-level message contracts to RabbitMQ without making RabbitMQ part of the conceptual model.

Architecture

logiCells message contract
    -> messaging adapter
    -> RabbitMQ
    -> messaging adapter
    -> consumer capability

Design rules

  • keep exchanges, queues, routing keys, and protocol details in deployment/integration configuration;
  • keep business message identity independent from broker delivery identifiers;
  • assume that reconnects and retries can lead to duplicate delivery unless the deployment contract proves otherwise;
  • use durable broker features when the application requires durable handoff;
  • monitor broker availability, queue depth, retry behavior, and consumer lag;
  • never embed passwords or long-lived secrets in documentation examples or committed configuration.

Protocols and versions

The exact RabbitMQ transport/protocol supported by a given adapter is version-dependent. Do not infer STOMP, AMQP, or another protocol from historical examples; verify the installed adapter capabilities.

Status

This page documents the integration pattern. Exact configuration keys and internal adapter class names are not part of the stable public contract.