Skip to content

Why the constructor requires a Management

AMQP 1.0 says how to move a message. It does not say whether the broker keeps it across a restart, whether a delivery count is written to disk, what a queue is, or where a rejected message goes. A backend that guessed would declare SurvivesRestart for a broker that loses a backlog, and the core would trust it. So amqp.New will not build without a Management:

messaging-amqp: a Management is required; nothing under at-least-once can be verified without one

What it is used for

A Management answers three things, and the backend is built on what it finds.

What the broker guarantees. Features is read once, at construction. SurvivesRestart and RestartLosesLastFailure are declared from it, never assumed: see Capabilities. A broker that is reconfigured is noticed by the next amqp.New.

Whether a queue is what the subscription needs. Describe reads the queue and its address's settings before the adapter attaches. The adapter binds to what the operator made and checks that it is durable, multicast, on the pattern's address, within a budget of at least MaxDeliver, and dead-letters somewhere that has a queue. Each failed check is a refusal that names it. The alternative is a subscription that attaches and silently runs with a volatile queue, or a dead-letter address that drops what it is sent.

Whether a publish would be kept. Routes tells the adapter whether anything receives from the address. A publish to an address with no queue is accepted by the broker and kept by nobody, which a publisher cannot see.

Why the operator owns the topology

The adapter verifies and never creates a durable queue: its error says "a bus attaches to a queue and never creates one". The practical effect is that a mis-typed DurableName fails naming the queue, where a bus that created queues would give it a fresh, empty one. Auto-create on the address defeats that, which is why the adapter checks Durable and the setup guide turns auto-create off. That is the trade: more setup, no silent drift.

Create and Delete are on the interface so that a Topology or an operator's tool can make queues over the same connection. The backend does not call them.

Why one broker ships

Artemis is the first Management because the module began there, and the suite runs against nothing else. The spine is generic: anything broker-specific lives in the Management. That makes another broker a matter of writing one, but it is a claim about the design and not about a tested broker. See Limits and gaps.