http://catamorphiclabs.com Emerging Technologies, in the palm of your hand Wed, 10 Mar 2010 22:15:11 +0000 http://wordpress.org/?v=2.7.1 hourly 1 http://catamorphiclabs.com/2009/04/18/data-processing-with-ruby-amqp-and-rabbitmq/comment-page-1/#comment-3 john Wed, 22 Apr 2009 17:34:39 +0000 http://catamorphiclabs.com/?p=4#comment-3 XMPP was considered as an option but did not fit into the problem domain as cleanly as AMQP. What we really needed was a persistent/recoverable notification system of legacy data needing to be processed. In this case it was drilled down to individual records. To do this in XMPP we would need a way to communicate that a record was processed which would require a middleman or the publisher of the legacy data to receive back replies that a job was finished. Another downpoint of XMPP in this problem domain is the ability to add workers and publishers dynamically. In XMPP this would require some sort of communication bridge that would allow publishers to see appropriate workers and then load balance between them. With RabbitMQ this was already built-in which allowed us to develop the new system more quickly. AMQP and RabbitMQ were chosen over XMPP due to their features and the specific problem domain. XMPP was considered as an option but did not fit into the problem domain as cleanly as AMQP. What we really needed was a persistent/recoverable notification system of legacy data needing to be processed. In this case it was drilled down to individual records. To do this in XMPP we would need a way to communicate that a record was processed which would require a middleman or the publisher of the legacy data to receive back replies that a job was finished. Another downpoint of XMPP in this problem domain is the ability to add workers and publishers dynamically. In XMPP this would require some sort of communication bridge that would allow publishers to see appropriate workers and then load balance between them. With RabbitMQ this was already built-in which allowed us to develop the new system more quickly. AMQP and RabbitMQ were chosen over XMPP due to their features and the specific problem domain.

]]> http://catamorphiclabs.com/2009/04/18/data-processing-with-ruby-amqp-and-rabbitmq/comment-page-1/#comment-2 bmuller Wed, 22 Apr 2009 14:44:50 +0000 http://catamorphiclabs.com/?p=4#comment-2 Why AMQP instead of XMPP? Why AMQP instead of XMPP?

]]>