any good OSGi remote service references/books/tutorials? [closed]

Question

First of all, I would like to know if OSGi remove service has been successfully implemented?

I am thinking of a good solution to the very messy system I am currently working on. Standalone java components scattered in a cluster of servers asynchrously communicating via JMS. (btw, it is an electronic trading platform).

I searched the web a while ago looking for a good reference but all I found were articles.

Can someone please point me to the right direction?

Thank you...

Answer 1

That depends entirely on what you mean by successfully, implemented and available. :-)

Generally speaking the situation is very sad: none of the readily available implementations really work well or offer what people seem to actually need in practice.

First of all it is important to distinguish between the "Remote Services" and "Remote Service Admin" specs. The former is simply a convention for exposing services in the OSGi service registry; the latter is "the real spec" and includes discovery, coordination between transports, selective import/export control etc. This is the hard bit, though there is no reason why a good toolkit/mini-framework for this should not be available as open-source package so that people can concentrate on writing discovery or transport bundles with minimal plumbing.

After looking at the work going on in the Apache CXF RI, ECF and Tuscany SCA (all of which we rejected for production use for various reasons) I started to work on a complete reimplementation, based off of the RI & CT as reference. This implementation is coming along nicely (a major new release is due soon) and is part of the commercial Nimble distribution by Paremus; see Remote Services. Disclaimer: I work for Paremus.

So, to answer your question: yes, there is at least one "successful" spec-compliant RemoteServiceAdmin implementation. Whether it is "available" or not is your call. :)

Answer 2

If its a distributed electronics trading platform - you are probably/possibly interested in low latency and robust recovery from service failure?

In both cases (IMO) the Nimble Remote Services implementation (thanks to Holger) really does lead the pack.