&gt; For smaller operations Redis is more than enough for pub&#x2F;sub.<p>I didn&#x27;t find that to be so at my last job, one of those smaller operations.<p>With Redis you&#x27;re forced to pick between two severely constrained options:<p>1. Use PUBLISH&#x2F;SUBSCRIBE.  This is nice if you want to have several listeners all receive the same message.  But if a listener is down, there&#x27;s no way for it to recover a message that it missed.  If there is no one listening, messages are just dropped.<p>2. Use LPUSH&#x2F;BRPOP.  This is nice if you want to have several workers all pulling from the same queue, but isn&#x27;t sufficient if you want to have several queues streaming from the same topic.  (E.g. one listener is responsible for syncing to ElasticSearch and another one is syncing to your analytics DB.)<p>I strongly prefer RabbitMQ.  Its model of exchanges and queues supports mixing and matching these semantics much more flexibly.