Designing RTI Routing Service adapters
The “layered databus” architecture pattern helps you design your system in a scalable and evolvable manner. Each layer shares only relevant data while optimizing the resources used for the connectivity domain. Typically, these layers are DDS domains that are connected by RTI Routing Service. However, specific layers may use a non-DDS technology that still requires connectivity with your core DDS databus.
Thankfully, Routing Service provides a platform for you to develop Processors and Adapters that enable connectivity even with non-DDS technologies. Processors allow you to manipulate and transform data through a route, while Adapters allow you to integrate with non-DDS technologies. For example - you can integrate with MQTT applications by creating an Adapter that can read and write your data formats using MQTT APIs.
Make the right design decisions from the start by accessing the Professional Services team’s experience guiding customers through design, development, and implementation of Routing Service plugins.
- The fundamentals about the RTI Routing Service plugin infrastructure
- Design guidance for creating your custom Processor(s)
- Design guidance for creating your custom Adapter(s)
- Kick-off development of your own custom plugins
The following criteria must be met before you can schedule this service:
- You must have previous Connext DDS experience and/or training. You must be familiar with the fundamental DDS concepts such as DDS entities, publish/subscribe APIs, Quality of Service configuration, discovery, transports, and configuration files.
This service typically is delivered in 8 hours.
Remote or Onsite
This activity can be delivered remote or onsite if bundled with other activities.