Koskamo

RabbitMQ best practices

Source-linked guidance on RabbitMQ fundamentals: queue durability, exchange routing, consumer acknowledgements, TTL and dead lettering, and connection/channel management. Scoped to RabbitMQ; not a general AMQP or messaging corpus.

Documents

Showing 1–5 of 5 documents

DocumentVersion

Durable queues for broker restart survival

Queues are durable or transient (non-durable). Metadata of a durable queue is stored on disk, so durable queues are recovered on node boot together with the messages in them that…

v1

Exchange types and routing

An exchange's type and its bindings implement the routing logic. Direct exchanges route to bound queues, streams, or exchanges using exact equivalence of the binding's routing…

v1

Long-lived connections and multiplexed channels

RabbitMQ protocols are TCP-based and assume long-lived connections for efficiency — a connection is not opened per protocol operation, and one client library connection uses a…

v1

Manual consumer acknowledgements and prefetch

In manual acknowledgement mode the consumer explicitly confirms each delivery: basic.ack for positive acknowledgements, and basic.nack or basic.reject for negative ones —…

v1

Message and queue TTL with dead lettering

TTL (time-to-live) can be set for messages and for queues. Per-queue message TTL is configured with the x-message-ttl queue argument at declaration or the message-ttl policy key;…

v1

Source, review, and usage
Published on Koskamo by
Koskamo editorial
Version
1
Documents
5 documents
Reviewed
2026-10-04
Agent lookups
0 in the last 90 days
Reuse
Original summaries; linked sources retain their own terms.
Review status
Maintained with the application; source links supplied

Original sources are linked on each document. Owner approval records a publishing decision; it does not imply independent fact checking.

Use this dataset from an agent

Agents can query it without an account. POST to /api/v1/retrieve, or connect an MCP client and call koskamo_retrieve with dataset: "rabbitmq-best-practices".

The JSON endpoint returns document text and source links in pages. Use limit and offset to retrieve more records; total gives the dataset size.

retrieve request
curl --fail-with-body 'https://koskamo.com/api/v1/retrieve' -H 'Content-Type: application/json' --data-raw '{"query":"rabbitmq-best-practices","dataset":"rabbitmq-best-practices","top_k":3}'

Change history

This dataset is maintained with the application. Its history is the Koskamo release history; the review date above is when its sources were last checked.