In the past year development of the AMQP gem was practicaly stagnating, as its original author Aman Gupta (@tmm1) was busy. A lot of bugs stayed unresolved, the code was getting old and out-dated and no new features or documentation were made.
At this point I started to talk with the RabbitMQ guys about possible collaboration on this. Actually originally I contacted VMware when I saw Ezra Zygmuntowicz looking for people to his cloud team, but when I found that VMware recently acquired the RabbitMQ project in London, I got interested. I signed the contract, switched from
script/console to Wireshark and the RabbitMQ Tracer and since November I’ve been happily hacking on the AMQP and AMQ-Protocol gems.
To introduce myself, my name’s Jakub Stastny (@botanicus) and I work as a Ruby contractor. I contributed to such projects as RubyGems, Merb and rSpec and I wrote my own framework called Rango, the only Ruby framework with template inheritance. I work with Node.js as well and I created Minitest.js, BDD framework for testing asynchronous code. My other hobbies are photography and travelling.
I asked Aman if I can take over the maintainership over the AMQP gem and he was happy to do so. At this point other two guys, Michael Klishin (michaelklishin) and Ar Vicco (arvicco) showed interest in the development, so we created ruby-amqp organisation at GitHub and forked the original code there, as well as a few other related repositories. The GitHub guys were happy to make our repository to be the main one, instead of just a fork, so since now, everything will be there (except the old issues which are still on tmm1’s fork and which we want to solve and close soon).
At the beginning, there were barely any tests at all, so it was basically impossible to tell if the changes I made break something or not. So I started to write some. In the later stage, when michaelklishin and arvicco joined the development, we rewrote the few original Bacon specs to rSpec 2 and now arvicco is porting his specs which he happened to write some time ago to the main repository. Arvicco has also written amqp-spec, superset of em-spec for testing the AMQP gem.
Currently the gem speaks only AMQP 0.8, which is more than 2 years old version, so probably the most important upcoming feature is support of AMQP 0.9.1. Because this is something what can be beneficial for other clients as well, I decided to create a new library called AMQ-protocol. It’s using rabbitmq-codegen as many others client libraries.
One of the main goals of this gem is to be really fast and memory-efficient (not for the sake of memory-efficiency itself, but because the garbage collector of MRI1 is quite weak) MRI. I’m about to create some benchmarks soon to see if the performance is better and how much.
AMQ-Protocol is still work-in-progress. It works, but it still needs some polishing, refactoring and optimizations, as well as documentation and tests.
I fixed a lot of bugs and I merged all the pending pull requests to the main repository. I’m going to write more about the changes once I’ll release AMQP 0.7. I released 0.7.pre recently, you can try it by running
gem install amqp --pre, which would be greatly appreciated. As the work on the test suite is still in progress now, the release process is kind of russian roulette at the moment.
I fixed quite a few bugs and obviously the fixed code is never backward-compatible with the old buggy one. One of the major changes is that
MQ#queues (as well as
MQ#fanouts etc) is not a hash anymore, but an array-like collection with hash-like2 behaviour. It does NOT override anonymous instances when another anonymous instance is created (as it used to do before) and it does support server-generated names. So instead of
MQ#queues[nil] = <first instance> and then
MQ#queues[nil] = <second instance>) it now just adds both instances to the collection and when it receives
Queue.Declare-Ok from the server, it updates the name to it.
The AMQP gem is very opinionated. If you don’t want to use EventMachine, you’re out of luck. You might want to use something more low-level like
IO.select or just another async library like cool.io. You might not even want to care about the asynchronous code at all.
It’d be great if we could have one really un-opinionated AMQP client library which only job would be to expose low-level API defined by the AMQP protocol without any abstraction like hidding channels etc. Such library would be intended for another library implementators rather than for the end users. AMQP is a complex protocol and because of some design decisions it’s pretty hard to design a good and easy-to-use (opinionated) client library for it. So some basic library which doesn’t make any assumptions would help others to play around and try to implement their own, opinionated libraries on top of this one without the need to manually implement the hard stuff like encoding/decoding or basic socket communication.
Are you interested in the AMQP gem development? Do you want to participate or do you have some questions? Feel free to contact me, either by comments under this blog post, or you can drop me an e-mail to firstname.lastname@example.org or drop by to Jabber MUC3 room at email@example.com where all the current maintainers usually are. And for all the news make sure you are following me on Twitter!
Written by: Jakub Stastny