We use it here in our business. Is the AMQP of choice for throughtput & latency (we use 0.18-20 version, planning to migrate to 0.34-5, we're testing to see if any regressions on this side. Memory footprint depends on how much messages will stay on queue if the queue doesn't suport paging, you must test by yourself. Persistent works good for us, scalability / failover worked so good with 0.18 series, in our 3-node cluster). The communication patterns req-reply, pub-sub we use here, works like a charm. By the means 'routing', í'm assuming you're talking about the broker exchanges (amq.topic). It's very efficient and fast.
On Wed, Oct 28, 2015 at 2:21 AM, Suman.Patro-TRN <[email protected] > wrote: > Hello Sir, > I am currently evaluating qpid broker for its > performance against other available brokers. So I would like to clear > certain queries regarding the same. > Can anyone suggest the way to test the qpid broker against the > following parameters: > 1. Throughput > 2. Latency > 3.Memory Footprint > 4.Persistence > 5.Scalability > 6.Failover mechanism > 7.Communication patterns support > 8.Security or cybersecurity involvement > 9.Routing algorithm used and its complexity > I would like to find statistics on the same by practical > evaluation , hence such a question. > Thanks and regards, > Suman > > Larsen & Toubro Limited > > www.larsentoubro.com > > This Email may contain confidential or privileged information for the > intended recipient (s). If you are not the intended recipient, please do > not use or disseminate the information, notify the sender and delete it > from your system. >
