Investigating Message Queueing systems

Bhavin Turakhia — Tue, 29 Dec 2009 07:32:12 +0000

In my constant quest for creating scalable systems and architecture a robust message queuing system was the missing link. I have begun reviewing some of the available options. This is a rough list of some of the interesting links I came across during this process -

http://wiki.secondlife.com/wiki/Message_Queue_Evaluation_Notes - A detailed comparison of queuing systems and their advantages and disadvantages. Covers RabbitMQ and Apache qpid and several others. The most comprehensive list of message queueing systems I found
http://stackoverflow.com/questions/731233/activemq-or-rabbitmq-or-zeromq-or - A list of links comparing various queueing systems
http://www.unlimitednovelty.com/2009/04/twitter-blaming-ruby-for-their-mistakes.html - A detailed critique on how twitter selected its message queue implementaions with comments from the developers at twitter and why they wrote their own queue. Do read the comments. They have a ton of meat
http://www.zeromq.org/whitepapers:brokerless - An interesting paper on brokerless message queues and the advantages thereof
http://gojko.net/2009/03/16/qcon-london-2009-upgrading-twitter-without-service-disruptions/ - Talks a bit about how twitter uses a messaging framework at the backend
http://blog.evanweaver.com/articles/2009/03/13/qcon-presentation/ - Evan Weaver’s talk on scaling twitter

Watch this space for more info …

http://wiki.secondlife.com/wiki/Message_Queue_Evaluation_Notes

The most detailed comparison of queuing systems and their advantages and disadvantages. Covers RabbitMQ and Apache qpid in detail and then several others. The most comprehensive list of message queueing systems.

http://stackoverflow.com/questions/731233/activemq-or-rabbitmq-or-zeromq-or

a list of links comparing various queueing systems

http://www.unlimitednovelty.com/2009/04/twitter-blaming-ruby-for-their-mistakes.html

A detailed critique on how twitter selected its message queue implementaions with comments from the developers at twitter and why they wrote their own queue. Do read the comments. They have a ton of meat

http://gojko.net/2009/03/16/qcon-london-2009-upgrading-twitter-without-service-disruptions/

Talks a bit about how twitter uses a messaging framework at the backend

http://blog.evanweaver.com/articles/2009/03/13/qcon-presentation/

Evan Weaver’s talk on twitters scalability issues and how they were solved

http://www.zeromq.org/whitepapers:brokerless

An interesting paper on differences between brokerless message queues and the advantages thereof

Bhavin's Blog » amqp

Investigating Message Queueing systems