<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">2013/5/14 ppafford <span dir="ltr"><<a href="mailto:phillpafford@gmail.com" target="_blank">phillpafford@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div id=":46u">So my question is, when would I break out the bullet points into smaller<br>
consumers? The consumer as is runs fine but I feel it's getting too large<br>
and needs to be refactored into smaller, more manageable processes.<br>
<br>
Should each bullet point be it's own consumer? I can see breaking them up<br>
into three consumers</div></blockquote></div><br>Do these steps have any interdependencies between them, e.g. C depends on A</div><div class="gmail_extra">being done?<br><br>How are your queues organized? Is there a single message that triggers all these operations?</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">If these steps can be described as a single unit of work, you can use a single consumer</div><div class="gmail_extra">with explicit acknowledgements and structure your code as a composed method [1],</div>
<div class="gmail_extra">then acknowledge the message at the end.</div><div class="gmail_extra"><br></div><div class="gmail_extra" style>If there are reasons to try to parallelize these steps, multiple queues and consumers may help.</div>
<div class="gmail_extra" style><br></div><div class="gmail_extra" style>1. <a href="http://codebetter.com/jeremymiller/2006/12/03/composed-method-pattern/">http://codebetter.com/jeremymiller/2006/12/03/composed-method-pattern/</a></div>
<div class="gmail_extra">-- <br>MK<br><br><a href="http://github.com/michaelklishin" target="_blank">http://github.com/michaelklishin</a><br><a href="http://twitter.com/michaelklishin" target="_blank">http://twitter.com/michaelklishin</a><br>
</div></div>