Hi Armin, Yes, for a couple years I used it in production. It handled a number of different applications, but the most intense was an image processing application that actually sent the images themselves as the message payload.
I don't know about the current state of ActiveMQ, but I can tell you that back then it couldn't handle the type of load that was necessary for our applications. We crashed it lots. ;-) That's actually what inspired the creation of PoCo::MQ! However, RabbitMQ seems very promising! I haven't tried it, but personally, if I needed a message queue for a big application *today*, I'd probably give that a try first just to see what it's like. At this point I think the biggest selling point of PoCo::MQ is that it's based on Perl, so if you already maintain a Perl stack and have Perl developers, it's a good choice. If you don't really care about setting up an Erlang environment, getting Erlang devs to customize it (or just don't care about customizing it) than RabbitMQ has a really vibrant growing community, so it seems like a good choice. Anyway, PoCo::MQ can work in production if you need it to. :-) Best regards, David. W dniu 29 marca 2012 23:06 użytkownik Armin Resch <ar...@reschab.net> napisał: > Hi, > > has anybody used this POE-based implementation of a Stomp server in a > production setting? It runs decently on my underpowered Linux-based > embedded test system but was wondering how it compares against other > implementations like Active-/RabbitMQ. > > Rgds, > -ar -- Blog: http://www.linguatrek.com Product: http://www.bibliobird.com
