Data-centric command and response
Most distributed systems include a data flow for command and response. Realizing this pattern on the Connext databus may seem obvious at first, but subtle implications of your data model can impact the performance, scalability, and even correctness of your applications. Through years of experience working with hundreds of customers, the RTI Professional Services team can teach you how to apply this pattern and the pitfalls to avoid when architecting your system.
An RTI expert will teach you how to implement the command and control pattern in Connext DDS, focusing on the two most common approaches:
- The Request-Reply pattern and API. This pattern has two roles:
- The requester (service consumer or client) sends a request message and waits for a reply message.
- The replier (service provider) receives the request message and responds with a reply message.
- The Objective State pattern. This pattern is a more data-centric approach to command and response, with components that are loosely coupled compared to request-reply. The pattern has two or more roles:
- Effectors provide current state and objective state commands and observe the requested objective state.
- Requesters provide the requested objective state and observe both the current and objective states.
- There can also be third parties in the system, typically acting as observers of state.
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 2-6 hours.
Remote or Onsite
This activity can be delivered remote or onsite if bundled with other activities.