title: Confused as to when you would use JMS (or a queue in general) versus a database
body: <p>When you store a message in a queue, isn't it more of meta data information so whoever pulls from the queue knows how to process the data?  the actual information in the queue doesn't always hold all the information.</p>
  
  <p>Say you have an app like Twitter, whenever someone posts a message, you would still need to store the actual message text in the database correct?</p>
  
  <p>The queue would be more used to broadcast to other subscribers that a new message has arrived, and then those services could take further action.</p>
  
  <p>Or could you actually store the tweet text in the queue also? (or you COULD, but that would be silly?)</p>
  
  <p>Could a queue message have status fields, which subscribers can change as they process their part of the work flow? (<strong>or would you do that in the db?</strong>)</p>
  
  <p>Just trying to get some clarification of when you would use a queue versus db.</p>