RabbitMQ – 1.5.5 Denied – 1.5.3 Rock On
No sooner had I got my RabbitMQ up and running did I find out that there wasn’t a perl module out to talk AMQP, so wrong. So google and twitter high jinx ensued and I found that there is a STOMP perl module and it seems a decent amount of people are talking STOMP with ruby. Awesomly enough there is a STOMP addon module you can compile up for RabbitMQ available from the RabbitMQ group itself. Unfortunately the 1.5.5 release of RabbitMQ doesn’t seem to play happily with the last version of the STOMP addon, suck. I did find out that the 1.5.3 RabbitMQ and STOMP addon are all good to go though. So I ended up backing my install down a couple version and once I grabbed the corresponding STOMPer it was back up and running. I’ve tested it with perl Net::Stomp and another developer has hit on it with a java AMQP implementation and I believe he’ll be giving it a go with ruby tonight.
I’m REALLY looking forward to messing with AMQP to pass things around. There’s more than a few places where I see we could have had a much smoother implementation/systems running with a decent message queue or broker running on the backside, especially a language independant one. I’m not a proponent (in my world anyway) of everything having to live on the BUS. It’s my belief that getting this component in our aresenal is going to allow us to make an evolutionary step forward in our systems.
2 Comments
Scott, thanks for posting this!
There was some discussion about how to use STOMP with 1.5.5 on the RabbitMQ list. Please could any folks interested in that refer to Matthias’ comments here: http://www.nabble.com/Stomp-Connector-not-working-in-tip-against-1.5.5-td23860618.html
Cheers
alexis
There is now a Perl client – check out rabbitmq-discuss or my watch list (‘monadic’) on github to find it …