"In short, any queue that could ever be a bottleneck needs management." - <a href="http://gettys.wordpress.com/2012/05/08/fundamental-progress-solving-bufferbloat/">http://gettys.wordpress.com/2012/05/08/fundamental-progress-solving-bufferbloat/</a><br clear="all">
<br>It's interesting to note that the same queue-management issues that appear on the Internet at large crop up not only within brokers like RabbitMQ themselves, but also within messaging client libraries. (You are trapped in a maze of congested queues, all different.) Ad-hoc solutions scale quite a long way inside a process, and not nearly so far across process boundaries; I wonder if implementing some "real" AQM within a process, e.g. in client libraries or within brokers, would help at all? Maybe for clustering and federation.<br>
<br>Regards,<br> Tony<br>-- <br>Tony Garnock-Jones<br><a href="mailto:tonygarnockjones@gmail.com" target="_blank">tonygarnockjones@gmail.com</a><br><a href="http://homepages.kcbbs.gen.nz/tonyg/" target="_blank">http://homepages.kcbbs.gen.nz/tonyg/</a><br>