<div>On Mon, Jan 14, 2013 at 7:18 AM, jdepp <span dir="ltr"><<a href="mailto:j_depp_99@yahoo.com" target="_blank">j_depp_99@yahoo.com</a>></span> wrote:</div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I would like to set up a rabbitMQ system that will be used for an application<br>
that has multiple data feeds and parsers to these feeds. Basically I will<br>
have one process that accesses all these feeds and places the data in queues<br>
and my parsers will be the consumers. I think after reading I will just have<br>
to create a producer to grab the feeds and place in queues and have the<br>
consumers access those queues. I am not sure as to what would then be the<br>
broker and how does this relate to my intended project. Does anyone know of<br>
any samples related to such a project type?<br></blockquote><div><br></div><div>Your scenario sounds like a fairly standard work queueing scheme and people do this with RabbitMQ all the time.</div><div><br></div><div>I am wondering what you mean by "I am not sure as to what would then be the broker." �In the Rabbit world, the 'broker' is the RabbitMQ server (or cluster of servers) itself. �A producer connects to the broker and publishes messages into it, while consumer connect to the broker and consume messages from queues. �Your queues exist within the broker.</div>
<div><br></div></div></div>