News for hackers. Stuff that matters.
Re:Message Queue Evaluation Notes by rdw on Wednesday January 11, 2012 @10:16AM (#3452070)
I'm the primary author (formerly Which Linden). Surprised to see this pop up here after all this time!

We wrote this almost three years ago, and at the time ZeroMQ was substantially less mature than it is now. In particular, the Python bindings were broken, weren't maintained by the ZeroMQ organization, and there was no indication they'd be production-ready by the time we needed it (which would have been within the next month or two).

More importantly, we were looking for something that handled our use case a little bit more fully. Our message-rate requirements were laughably small, so what we really wanted was software that gave us an "inbox" for each of millions of users. We also weren't looking forward to implementing failover, consistency, and sharding from scratch.

Edit: corrected timeline.

Re:Message Queue Evaluation Notes by fzzzy on Wednesday January 11, 2012 @12:56PM (#3452818)
Hi rdw! What are you up to now? I don't have any contact info for you and haven't seen you on irc in forever.

(You might not recognize this nick, this is Donovan)

Re:Message Queue Evaluation Notes by DEinspanjer on Wednesday January 11, 2012 @10:44AM (#3452185)
Do you know what they ended up settling on?
Re:Message Queue Evaluation Notes by rdw on Wednesday January 11, 2012 @11:46AM (#3452460)
No out-of-the-box solution was used. The system remained a menagerie of different messaging techniques (database, udp, in-memory storage), and the company just spent time improving the reliability and performance of these existing systems individually.
Re:Message Queue Evaluation Notes by pavlov on Wednesday January 11, 2012 @10:21AM (#3452096)
Thanks for the explanation!