Cross-platform, cross-language messaging system?

Question

I\'m developing a set of applications that work together to create a system for processing metering data. There\'s several reasons I want to have them loosely coupled and the sy

Answer 1

You could use an ESB (Enterprise Service Bus) like Mule. The idea is that you send your messages to the Bus in any way you want (JMS, http, email) and the bus does the routing for you. I don't know if there are .NET bindings, but even if there aren't any available, you can build your own using an extension mechanism. Of course, this means you need to set up a bus somewhere.

Answer 2

Open Message Queue (Open MQ) is included in the GlassFish application Server and also runs stand-alone. It starts up in a few seconds, and supports Java and C client. Stomp support is currently in development in version 4.4.

Answer 3

If you want a multilanguage "standard" -- meaning you are not tied to using a specific broker / intermediary like ActiveMQ, SonicMQ, or WebsphereMQ -- I strongly suggest you look at the AMQP standard (http://www.amqp.org) and related brokers (RabbitMQ, QPid, OpenAMQ; see http://www.amqp.org/confluence/display/AMQP/AMQP+Products).

Answer 4

activemq

http://activemq.apache.org/cross-language-clients.html

Supports all the following protocols

• OpenWire
• REST
• Stomp
• WS Notification
• XMPP
• AMQP

Thanks Paul

Answer 5

Have you considered MPI?

Answer 6

As Paul mentioned, try ActiveMQ which supports many language clients and wire protocols.

BTW ActiveMQ 6.x will probably be using Google's protocol buffers as one of its underlying wire transports :)

I've used Apache ActiveMQ on many projects to great success. Its the most popular and powerful open source message broker around today.

Incidentally on .Net / C# the ActiveMQ project has created the NMS API which is a standard API for communicating with message brokers on the .Net platform which is now integrated into Spring.Net