# ankusa_rabbitmq v0.7.0 - Table of Contents

> Ankusa.Sink adapter publishing delivered hooks to a RabbitMQ exchange.

## Pages

- [ankusa_rabbitmq](readme.md)
- [Changelog](changelog.md)

## Modules

- [Ankusa.Sink.RabbitMQ](Ankusa.Sink.RabbitMQ.md): Publishes delivered hooks to a RabbitMQ **exchange**. Never touches a queue
— binding a queue to the exchange, and everything downstream of that, is
the consumer's job, not this sink's. That mirrors real AMQP topology
ownership: producers own exchanges, consumers own their own queues.
- [Ankusa.Sink.RabbitMQ.Application](Ankusa.Sink.RabbitMQ.Application.md): Starts the connection tree (`Ankusa.Sink.Connections`) for the
`Ankusa.Sink.RabbitMQ.Connection`s `Ankusa.Sink.RabbitMQ` opens on demand
from `publish/4`, one per instance and `{url, exchange}`.
- [Ankusa.Sink.RabbitMQ.Connection](Ankusa.Sink.RabbitMQ.Connection.md): One AMQP connection + confirm-mode channel per `{instance, url, exchange}`.
Declares the configured exchange whenever it opens the channel (idempotent) —
never a queue; queue ownership belongs to consumers, not this sink.