Simple asynchronous AMQP driver for Ruby/EventMachine This library works with Ruby 1.8, Ruby 1.9, JRuby and Rubinius, and is licensed under the Ruby License.
This library was tested primarily with RabbitMQ, although it should be compatible with any server implementing the AMQP 0-8 spec.
To use examples with RabbitMQ, first install the broker. If you have Mercurial and Erlang/OTP installed, here is how to do it in 4 lines:
hg clone http://hg.rabbitmq.com/rabbitmq-codegen
hg clone http://hg.rabbitmq.com/rabbitmq-server
cd rabbitmq-server
make run
Then have a look at the various bundled examples:
ruby examples/mq/pingpong.rb # 1-1 communication using amq.direct
ruby examples/mq/clock.rb # 1-N communication using amq.fanout
ruby examples/mq/stocks.rb # 1-subscriber communication using amq.topic
ruby examples/mq/multiclock.rb # header based routing (new rabbitmq feature)
ruby examples/mq/ack.rb # using ack
ruby examples/mq/pop.rb # pop off messages one at a time
ruby examples/mq/hashtable.rb # simple async rpc layer
ruby examples/mq/primes.rb 4 # parallelized prime number generation
ruby examples/mq/logger.rb # simple logging api
For high level API documentation see MQ class. For more details into the lower level AMQP client API, run the simple client example:
ruby examples/amqp/simple.rb # low-level AMQP api
ruby examples/mq/internal.rb # low-level Queue/Exchange api
Or refer to protocol/doc.txt, which enumerates packets sent between a server and client during a typical session, in both binary and decoded formats.
To use AMQP gem from web applications, you would need to have EventMachine reactor running. If you use Thin, you are set: Thin uses EventMachine under the hook.
With other web servers, you need to start EventMachine reactor in it's own thread like this:
Thread.new { EM.run }
because otherwise EventMachine will block current thread. Then connect to AMQP broker:
AMQP.connect(:host => "localhost", :user => "guest", :pass => "guest", :vhost => "/")
In a Ruby on Rails app, probably the best place for this code is initializer (like config/initializers/amqp.rb). For Merb apps, it is config/init.rb. For Sinatra and pure Rack applications, place it next to other configuration code.
Same separate thread technique can be used to make EventMachine play nicely with other libraries that would block current thread (like File::Tail).
To run the test suite make sure you have bacon gem installed and run:
rake spec
The lib/amqp/spec.rb file is generated automatically based on the AMQP specification. To generate it:
rake codegen
(c) 2008—2010 Aman Gupta (tmm1)
This project was inspired by py-amqplib, rabbitmq, qpid and rubbyt. Special thanks to Dmitriy Samovskiy, Ben Hood and Tony Garnock-Jones.
- RabbitMQ (Rabbit Technologies, Erlang/OTP, MPL)
- ZeroMQ (iMatix/FastMQ/Intel, C++, GPL3)
- OpenAMQ (iMatix, C, GPL2)
- ActiveMQ (Apache Foundation, Java, Apache2)
-
Steve Vinoski explains AMQP in his column, Towards Integration
-
John O'Hara on the history of AMQP
-
Dmitriy's presentation on RabbitMQ/AMQP
-
Pieter Hintjens's background to AMQP
-
Barry Pederson's py-amqplib
-
Ben Hood on writing an AMQP client
-
Dmitriy Samovskiy introduces Ruby + QPid + RabbitMQ
-
RabbitMQ's AMQP protocol code generator
-
Erlang Exchange presentation on the implementation of RabbitMQ (and on the LShift blog)
-
Jonathan Conway's series on RabbitMQ and using it with Ruby and Merb: One, Two, Three, Four
-
Open Enterprise's series on messaging middleware and AMQP: Part 1, Part 2, Part 3
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent