Glossary
AMQP (Advanced Message Queuing Protocol)
AMQP is an open standard protocol for message-oriented middleware. It defines how messages are formatted, routed, and reliably delivered between applications via a central broker, making it a backbone of enterprise integration and event-driven architectures.
General definition
AMQP, or the Advanced Message Queuing Protocol, is an application-layer protocol standardised by OASIS that governs how producers, brokers, and consumers exchange messages. Unlike point-to-point socket connections, AMQP routes messages through a message broker (such as RabbitMQ or ActiveMQ), which handles queuing, persistence, acknowledgements, and fan-out delivery.
- Guaranteed delivery with acknowledgement and requeue semantics
- Flexible routing via exchanges (direct, topic, fanout, headers)
- Message persistence so nothing is lost if a consumer is temporarily offline
- Binary wire format for efficiency in high-throughput environments
AMQP is widely used for backend service integration, job queues, event streaming, and notification pipelines. It is distinct from real-time chat protocols like XMPP, though both can carry messaging traffic.
In the Ethora ecosystem
Ethora’s Chat SDK uses XMPP for real-time user-to-user and group messaging, while backend service communication in an Ethora deployment can integrate with AMQP-based brokers for event fan-out, audit pipelines, and webhook dispatch. In a self-hosted deployment you control the full broker configuration, enabling you to wire AMQP queues directly into your enterprise infrastructure.
For regulated environments such as healthcare, routing chat events through a persistent AMQP broker adds an audit-ready delivery guarantee layer that shared cloud services cannot provide.
