title: Websphere MQ - Pub / Sub
body: <p>We are working on establishing an architecture where we will have two processing applications needing to receive information from a single queue (They will use the data in entirely different ways).  What is considered best practice / path-forward for IBM WebSphere MQ in this situation?</p>
  
  <ol>
  <li>Pub / Sub - One publisher and "n" number of subscribers?</li>
  <li>The folks administering our MQ have suggested a fan out (trigger that reads from a named list and distributes to multiple queues) - This doesn't seem like a good idea to us. </li>
  <li>Others?</li>
  </ol>
  
  <p>Any suggestions or input would be greatly appreciated. </p>