<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Hello, <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I am curious if RabbitMQ addresses the following use case.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>A single queue. Persistent.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>A producer creates messages fast (average 10 msg/sec).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Consumers process messages slow (average 1 msg/sec). Thus 10 consumers are required to keep up.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Challenge 1: Some messages (< 1%) are related and need to be processed in order. If two dependent messages are less than 10 messages apart, they are processed in parallel. That’s a problem.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Obvious solution: create 10 queues, each with a different key, and each with only one consumer. But:<o:p></o:p></p><p class=MsoNormal>* Non-related messages are unnecessarily sequenced. When the key distribution is not exactly even, one queue may have a backup while another is idle.<o:p></o:p></p><p class=MsoNormal>* Complex to configure for differently sized systems.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Challenge 1+: earlier message could fail processing and be re-queued with a delay. Obvious solution doesn’t fix that.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Desired solution: Queue knows what messages are being processed / re-queued and holds messages with the same key.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>But that’s not all. Consumers are clustered, with load balancing (scalability) and failover (availability).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Challenge 2a: related messages must still be processed by the same consumer (and thus loadbalanced to the same node).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Challenge 2b: related messages must be processed in order across node failures.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Obvious solution: Solution to 1 and migrate file store and consumer from failed node to another node. But:<o:p></o:p></p><p class=MsoNormal>* Need external system to manage migration.<o:p></o:p></p><p class=MsoNormal>* Very complex to configure for differently sized systems (different workloads, different node sizes and different cluster sizes).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Desired solution: Solution 1 queues, and coordinate across nodes what keys have messages being processed or re-queued. Will affect throughput (we need only 250 msg/sec).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks…<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Roger<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>PS: Please copy the response to my email (roger dot fischer at abb dot Ventyx dot com) as I am not a subscriber of the list.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div>
<br><br><br> </b>
<b>Mindshare 2012 | May 8-10 | Orlando, FL </b>
<br><b>More details coming soon. </b>
<br><br> </b>
<b>Dates and location for European Mindshare coming soon. </b>
<br><br> </b>
DISCLAIMER:<HR>This email message and all attachments transmitted </b>
with it are for the sole use of the intended recipient(s) and may </b>
contain confidential and privileged information. Please DO NOT </b>
forward this email outside of the recipient's Company unless </b>
expressly authorized to do so herein. Any unauthorized review, use, </b>
disclosure or distribution is prohibited. If you are not the intended</b>
recipient, please contact the sender by reply email and destroy all </b>
copies of the original message.<P>Any views expressed in this email </b>
message are those of the individual sender except where the sender </b>
specifically states them to be the views of Ventyx.<hr>
<br></body></html>