Greg, On 27 April 2015 at 16:28, Greg Keogh <[email protected]> wrote:
> ... I'm looking for a painless way of getting multiple components of an > app suite to freely broadcast messages amongst themselves. I've used UDP > for this before, but it has size limits and you have to deal with low level > things like multiple MAC address and so forth. > If you need programmable message routing that scales with your imagination, then I recommend a message broker like RabbitMQ [1] or 0MQ [2]. Depending on your definition of "painless", a dedicated broker process might be overkill, but a message broker is such a useful piece of infrastructure that you will be wondering how your application ecosystem ever functioned without one. If you want a testimonial, RabbitMQ has been outstanding for us -- almost a silver bullet. The .NET client library is functional and all managed code, if a bit old-fashioned (or neglected, depending on your expectations). The documentation is generally very good. The server's installation footprint is not insignificant, however, because it needs the Erlang runtime (nothing like .NET Framework or JRE, though). [1] http://www.rabbitmq.com [2] http://zeromq.org -- Thomas Koster
