title: Architectural comments for queueing with RabbitMQ?
body: <p>I basically need a queueing technology that will enable to queue messages. These messages will then later be transmitted as SMS texts. RabbitMQ seems to be quite a good fit after I glossed over the apis. </p>
  
  <p>My current architecture plans:</p>
  
  <ol>
  <li>clients queue messages in RabbitMQ.</li>
  <li>Another daemon will reads messages off RabbitMQ and sends those off to a 3rd party SMS gateway. The daemon should be able to spawn multiple listener threads.</li>
  <li>I plan to host everything on slicehost.com using an Ubuntu Hardy.</li>
  </ol>
  
  <p>Do you forsee any problems with this design? Since I have cursory knowledge of Erlang, I have no ideas on how to run it in a production environment. If you have any experience with Erlang or RabbitMQ, I'd like to hear your war stories. </p>