title: RabbitMQ / ActiveMQ or Redis for over 250,000 msg/s
body: <p>Eventhough redis and message queueing software are usually used for different purposes, I would like to ask pros and cons of using redis for the following use case:</p>
  
  <ul>
  <li>group of event collectors write incoming messages as key/value . consumers fetch and delete processed keys</li>
  <li>load starting from 100k msg/s and going beyond 250k in short period of time (like months) target is to achieve  million msg/s</li>
  <li>persistency is not strictly required. it is ok to lose non-journaled messages during failure</li>
  <li>performance is very important (so, the number of systems required to handle load)</li>
  <li>messages does not have to be processed in the order they arrive</li>
  </ul>
  
  <p>do you know such use cases where redis chosen over traditional message queueing software ? or would you consider something else ? </p>
  
  <p>note: I have also seen this but did not help: 
  <a href="https://stackoverflow.com/questions/6169658/real-time-application-newbie-node-js-redis-or-rabbitmq-client-server-how">Real-time application newbie - Node.JS + Redis or RabbitMQ -&gt; client/server how?</a> </p>
  
  <p>thanks </p>