title: Should I use separate connections for Pub and Sub with Redis?
body: <p>I have noticed that <em>Socket.io</em> is using two separate connections for Pub and Sub to <em>Redis</em> server. Is it something that could improve the performance? Or is it just purely a move towards more organized event handlers and code? What are the benefits and drawbacks of the two separate connections and one single connections for publishing and subscribing.</p>
  
  <p><strong>P.S.</strong> The system is pushing about an equal number of messages that it is receiving. It pushes updates to the servers, which are on the same level in the hierarchy, so there is no master, pushing all of the updates, or slave, consuming the messages. One server would have about 4-8 subscriptions and it will send the messages back to these servers.</p>
  
  <p><strong>P.S.S.</strong> Is this more of a job for a purpose-built job queue? The reason I am looking at Redis. is that I am already keeping some shared objects in it, which are used by all servers. Is message queue worth adding yet another network connection?</p>