OSGi Remote Services and ECF
Chapter 13 in the OSGi 4.2 compendium specification describes a new service-oriented architecture (SOA) standard. This standard uses the OSGi service registry to expose remote services...i.e. OSGi services that are actually implemented in processes distributed on a network.
ECF's support for this standard is implemented as a layered set of application programming interfaces (APIs). This layered and modular structure allows service builders and service consumers to use an 'ala carte' model for defining, creating, deploying, integrating, and running distributed services. Such an 'ala carte' model of modularity is helpful for two primary reasons:
- It helps reduce overall system complexity. By only including technologies that are actually necessary, rather than including/requiring functionality needed to support other use cases. For a lucid presentation about the value of modularity for simplifying complicated systems, see How Module Systems Drive Architectures.
- It provides flexibility. This flexibility allows consumers to mix-and-match transport protocols and serialization formats, supports interoperability, and easy integration with existing systems, and supports use of synchronous and/or asynchronous invocation patterns as needed.
Here is a diagram showing the relationship between these APIs.
Here are two examples (with source) showing the use of ECF's remote services to expose and access a 'hello world' remote service.
- RFC119 - Getting Started with ECF's RFC119 Implementation
- Remote Services API - Getting Started with Using the ECF Remote Services API
|Eclipse Communication Framework|
|API Documentation • Javadoc • Providers • ECF/Bot Framework|
|Servers • Shared Editing • Shared Code Plug-in|
|Development Guidelines • Integrators Guide|