title: Mocking out a message queue
body: <p>My application uses numerous message queue connections which makes it difficult for me to run my environment locally. Currently, I'm simply connecting to the DEV or TEST environment which can be problematic when there are issues in those environments.</p>
  
  <p>What are some ways that I could build a fake message queue service for local development? I would like to have some of the following functionality:</p>
  
  <ul>
  <li>Handling of concurrent reads/writes from multiple processes</li>
  <li>Reliable message consumption (via visibility timeouts)</li>
  <li>Guaranteed at-most-once delivery</li>
  </ul>
  
  <p>Is this possible?</p>
  
  <p>Things I've considered include:
  - building a mock JMS service and deploying it somewhere (or run it up in a VM)
  - implement a mock service which returns different responses based on the incoming message</p>
  
  <p>Anything else?</p>