Comments on: Sending CouchDB Update Notifications to RabbitMQ. http://www.joeandmotorboat.com/2009/06/05/sending-couchdb-update-notifications-to-rabbitmq/ Fri, 05 Mar 2010 06:54:53 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Fun with the CouchDB _changes feed and RabbitMQ. – Joe’s Blog! http://www.joeandmotorboat.com/2009/06/05/sending-couchdb-update-notifications-to-rabbitmq/comment-page-1/#comment-1094 Fun with the CouchDB _changes feed and RabbitMQ. – Joe’s Blog! Thu, 07 Jan 2010 23:59:06 +0000 http://www.joeandmotorboat.com/?p=913#comment-1094 [...] HTTP streams it seemed like it would be a perfect fit for use with CouchDB. A while back I wrote some code to push update notifications to RabbitMQ and a commenter mentioned using the _changes feed instead. Combining the _changes feed [...] [...] HTTP streams it seemed like it would be a perfect fit for use with CouchDB. A while back I wrote some code to push update notifications to RabbitMQ and a commenter mentioned using the _changes feed instead. Combining the _changes feed [...]

]]> By: zdzolton http://www.joeandmotorboat.com/2009/06/05/sending-couchdb-update-notifications-to-rabbitmq/comment-page-1/#comment-942 zdzolton Mon, 08 Jun 2009 15:49:09 +0000 http://www.joeandmotorboat.com/?p=913#comment-942 Hey, you should port this code to use the new _changes API, in trunk, à la: http://jchrisa.net/drl/_design/sofa/_show/post/Simple-Wins Hey, you should port this code to use the new _changes API, in trunk, à la:

http://jchrisa.net/drl/_design/sofa/_show/post/Simple-Wins

]]> By: evgen http://www.joeandmotorboat.com/2009/06/05/sending-couchdb-update-notifications-to-rabbitmq/comment-page-1/#comment-940 evgen Sun, 07 Jun 2009 04:26:20 +0000 http://www.joeandmotorboat.com/?p=913#comment-940 One advantage of doing this with the native erlang client is that you could actually plug it in to CouchDB at the server level rather than using the rather weak update notification that CouchDB currently supports (or the only-slightly-less-useless version of update notification that is on the way...) One advantage of doing this with the native erlang client is that you could actually plug it in to CouchDB at the server level rather than using the rather weak update notification that CouchDB currently supports (or the only-slightly-less-useless version of update notification that is on the way…)

]]> By: joe http://www.joeandmotorboat.com/2009/06/05/sending-couchdb-update-notifications-to-rabbitmq/comment-page-1/#comment-939 joe Sat, 06 Jun 2009 22:12:51 +0000 http://www.joeandmotorboat.com/?p=913#comment-939 Nah, no reason, it would likely be pretty easy to do with erlang and the amqp client. I just liked how simple it was to do with Ruby. Nah, no reason, it would likely be pretty easy to do with erlang and the amqp client. I just liked how simple it was to do with Ruby.

]]> By: Abhay Kumar http://www.joeandmotorboat.com/2009/06/05/sending-couchdb-update-notifications-to-rabbitmq/comment-page-1/#comment-938 Abhay Kumar Sat, 06 Jun 2009 22:03:39 +0000 http://www.joeandmotorboat.com/?p=913#comment-938 Although Ruby is definitely quick out of the box, is there any particular reason you wouldn't just plug this into couchdb via the erlang-amqp client? Although Ruby is definitely quick out of the box, is there any particular reason you wouldn’t just plug this into couchdb via the erlang-amqp client?

]]>