title: MQ Cache? good or bad idea?
body: <p>I am wondering if MQ can be used as a state cache for monitoring? And is this a good idea or not?</p>
  
  <p>In theory you can have many sources (monitoring agents) that detect problem states and distribute them to subscribers via an MQ system such as RabbitMQ. But has anyone heard of using MQ systems to cache the state, so when clients initialize, they read from the state queue before subscribing to new state messages? Is that a bad way to use MQ?</p>
  
  <p>So to recap, a monitor would read current state from a state queue then setup a subscription queue to receive any new updates. And the state queue would be maintained by removing any alerts that are no longer valid by the monitoring agents that put the alert there to begin with.</p>
  
  <p>Advantage would be decentralized notification and theoretically very salable by adding more mq systems to relay events. </p>