As general background to the conversation, the following summarizes some nice anti-patterns in the area:<br><br><a href="http://www.engineyard.com/blog/2011/5-subtle-ways-youre-using-mysql-as-a-queue-and-why-itll-bite-you/">http://www.engineyard.com/blog/2011/5-subtle-ways-youre-using-mysql-as-a-queue-and-why-itll-bite-you/</a><br>
<br>These are good things to watch out for, since they almost spontaneously self organize in a lot of systems we've seen. :-)<br><br>Best regards,<br>Jerry<br><br><div class="gmail_quote">On Mon, Aug 13, 2012 at 2:38 PM, Mark Feeney <span dir="ltr"><<a href="mailto:mark.feeney@gmail.com" target="_blank">mark.feeney@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi, Emile.<br>
<br>
Thanks for the response!<br>
<div class="im"><br>
> If you find yourself performing SELECT queries on the messages, and<br>
> their order is less important then consider using a relational database<br>
> instead.<br>
<br>
</div>I do have some fairly tricky SELECT statements to get the next item<br>
form my current queue system, so this is a good point.<br>
<div class="im"><br>
> If not all messages are routed in an identical way, or you find yourself<br>
> writing lots of database trigger code then I would suggest using a<br>
> message broker. RabbitMQ can cope with long persistent queues, with<br>
> messages of variable sizes.<br>
<br>
</div>This sounds like another good guideline. �Right now I don't really<br>
have any message routing on the ingress side of my ad-hoc queue<br>
system. �The SELECT statement that gets the next message ends up doing<br>
some fiddly logic to get the "correct" message out, and this can cause<br>
issues, esp. with larger queues. �I'm considering routing messages to<br>
the correct queue when they first arrive, so rabbit seems like a good<br>
fit for this sort of thing.<br>
<div class="im"><br>
> If performance is a consideration then you should run some benchmarks<br>
> for your expected workload.<br>
<br>
</div>Of course. �Thanks again for your response, I'm getting a clearer<br>
picture of how I might use rabbitmq.<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
Mark.<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</div></div></blockquote></div><br>