News for hackers. Stuff that matters.
Re:ActiveMQ: Not ready for prime time by justincormack on Thursday May 26, 2011 @01:37PM (#2588659)
zeromq does not persist messages so you can lose them and need to adjust your infrastructure around this. If you are used to network programming that should be fine, just build persistence in to your protocol where you need it, ie reply after you have committed to persistent storage.
Re:ActiveMQ: Not ready for prime time by jrockway on Thursday May 26, 2011 @08:33PM (#2589983)
It persists messages in one direction. Imagine you have a publish subscribe situation where you have a few apps subscribed to a publisher. If one of those apps goes down, the publisher will make a note and store the messages until it comes back. When the app comes back, it will get all the messages it missed. It's really a wonderful thing if you were going to implement peer-to-peer pub/sub yourself.

It's also nice in applications like Mongrel2. Make an http request, in your browser, start up your web server, and the request completes! Great for development, where sometimes you switch to the browser faster than your app can restart after a change. With Mongrel2 (and thanks to 0MQ), you don't even notice the race condition.

Re:ActiveMQ: Not ready for prime time by calloc on Thursday May 26, 2011 @06:21PM (#2589645)
ZeroMQ can persist messages to disk in high water mark situations, so once it hits memory pressure it can put it to disk, but it won't read from disk on crash...