This Documentation Has Moved to rubyamqp.info

Which versions of the amqp gem do the guides cover?

Documentation structure and how to read these guides

We recommend that you read the documentation guides in the order that they are listed. The Getting Started guide is written as a tutorial that
describes several typical applications and their problem scope, then provides full code examples and finally breaks them down
into smaller pieces that are explained in detail.

Once you are finished with the tutorial, reading the other guides in sequence will gradually explain all of the AMQP 0.9.1 features that are relevant to
application developers, including application design concerns and common practices. At present, some guides are yet to be written
but most of the content is concentrated in just 3-4 guides that are about 80% finished and provide plenty of examples.

A simple, 2 page long introduction to the AMQP 0.9.1 model, focusing on what purpose individual features have. Reading
other documentation guides will be easier when you are armed with this knowledge: a lot of the AMQP & RabbitMQ power
comes from the AMQP Model.

What AMQP queues are. How to declare AMQP queues. When and how to use server-named and explicitly named queues. How to subscribe
for “push” message delivery. What message acknowledgements are. How to access AMQP message metadata. How to fetch (“pull”) messages
from queues on demand. How to bind and unbind a queue to an exchange. How to delete a queue.

What AMQP exchanges are. Concept of binding. How to declare AMQP exchanges. How different exchange types route messages and common
use cases. How to publish messages, especially how to do it reliably. What AMQP transactions are. What Publisher Confirms are. When
messages are returned. How to delete an exchange.

Authors

Tell us what you think!

Please take a moment to tell us what you think about this guide on Twitter or the Ruby AMQP mailing list.
Let us know what was unclear or what has not been covered. Maybe you do not like the guide style or grammar or discover spelling mistakes. Reader feedback is
key to making the documentation better.