Re: [ecf-dev] tutorial idea: OSGi remote services for existing services

[Scott Lewis <slewis@xxxxxxxxxxxxx>]

On 10/7/2014 2:54 AM, Markus Alexander Kuppe wrote:
> On 10/05/2014 05:21 PM, Scott Lewis wrote:
> > Perhaps you have some thoughts/suggestions on some existing services to
> > turn into OSGi Services?
> Jenkins has an REST API and is a somewhat popular OSS project, but also
> has commercial offerings.

Hmm.    Although clearly there are a number of developer/development 
services...commercial and OSS (e.g. github, Jenkins, bugzilla, Eclipse, 
etc)...I have mixed feelings about focusing this first tutorial on dev 
services.     I would like to try to make the point that ECF's Remote 
Services is not *only* for developer/development/tooling services...but 
rather is a great way to expose all manner of 'cloud services'.

There are lots of technical advantages to using ECF's Remote Services 
impl to do this...e.g. use of open standards, all the technical virtues 
of OSGi services (service versioning, security, dynamics, service 
dependencies, injection frameworks, RSA mgmt, etc., etc), and 
crucially:  the ability to not have to modify the service/server *at 
all*.   The integration and/or migration value of this is potentially 
very high, I believe.

I would like to try to find a service that is outside of the realm of 
dev/developer/dev tooling.   Of course, with some community 
collaboration we could potentially create several 
examples/tutorials...with both dev services and non-dev services. I 
would very much like to do all of them, but I can't currently commit to 
doing several tutorials myself.

For example of non-dev services: any emerging IoT services?, storage 
services?, data analytics services?, comm/messaging services?, etc? that 
people would like to see (or have already been) abstracted into a simple 
OSGi service (i.e. a java interface)?

Thanks,

Scott