Skip to content

Core Messaging Service

Jump to bottom
Nuno Nunes edited this page Sep 16, 2010 · 5 revisions

On this section we describe the usage of the core messaging service and detail the software implementing it.

Basic description of the messaging component

To fill in.

Open issues

0MQ

0MQ is a messaging mechanism that seems like a pretty good base for our design. It is extremely simple to use, it is higly efficient, fast and has bindings for a great many programming languages.

It has it's drawbacks, of course, not the least of one being lack of persistence of the messages. It is a brokerless solution.

One way we could introduce a boker into the mix (if we decide we really need it), would be to, for exemple, use a RabbitMQ broker into the mix, since it has support for 0MQ messaging (as an add-on / built-in?).

Other possibilities

These other systems are under consideration, please add whatever you think is relevant about each one here.

  • SapoBroker - I've used it and like it. It is written in Java (I'm not sure anything else in the echosystem will be, so we'd need to have java support just for this one system) and it had (a long time ago) ;-) bindings for a few languages;

  • OpenAMQ - Since the main guys behind it (iMatix) are abandoning it soon, I don't think this will turn out to be a good alternative for us. Thoughts?

  • Redis - This is a swiss army-like data store which, among other things, implements a messaging system. Might be good to look at this, especially since it is also under consideration for the Core Data Store system.

Clone this wiki locally