7. Software Development Kit¶
You can extend the out-of-the-box behavior of Routing Service through its Software Development Kit (SDK). The SDK provides a set of public interfaces that allow you to control Routing Service execution as well as extend its capabilities.
The SDK is divided in the following modules:
- RTI Routing Service Service API:
This module offers a set of APIs that allow you to instantiate Routing Service instances in your application. This allows you to run Routing Service as a library, as described in Section 3.2. - RTI Routing Service Adapter API:
Adapters are pluggable components that allow Routing Service to consume and produce data for different data domains (e.g. Connext DDS, MQTT, raw Socket, etc.). This module offers a set of pluggable APIs to develop custom Adapters, which you can use through shared libraries or through the Service API. By default, Routing Service is distributed with a builtin DDS adapter that is part of the service library. - RTI Routing Service Processor API:
Processors are event-oriented pluggable components that allow you to control the forwarding process that occurs within a Route. This module offers a set of pluggable APIs to develop custom Processors, which you can use through shared libraries or through the Service API. - RTI Routing Service Transformation API:
Transformations are data-oriented pluggable components that allow you to perform conversions of the representation and content of the data that goes through Routing Service. This module offers a set of pluggable APIs to develop custom Transformations, which you can use through shared libraries or through the Service API.
Table 7.1 shows which modules are available for each API, along with links to the API documentation.
| Language API | Available Modules |
|---|---|
| RTI Routing Service C API |
|
| RTI Routing Service C++ API |
|
| RTI Routing Service Java API |
|