DDS Best Practices

RTI Connext DDS is a powerful platform that abstracts many difficult parts of distributed system design. However, like any powerful technology, it must be used in optimal ways to get the most out of it. There may be multiple ways to accomplish the same goal, but the approaches can differ in performance or resource utilization. These best practices provide rules on designing your distributed system and architecting applications that use RTI Connext DDS.

You can contribute by commenting on existing best practice articles, or by creating new best practices here (requires logging in).

Defining Topic names in source code in each application is readable in example code, but is not ideal for a real system.

5222 reads — 0 comments

For each data type, indicate to RTI Connext DDS the fields that uniquely identify the data object.

7312 reads — 0 comments

Mapping all of your data model to opaque bytes or strings (even XML strings) is a bad practice for several reasons, some obvious and some subtle:

4704 reads — 0 comments

When you write keyed data, the RTI Connext DDS has to send the unique identifier of each instance along with the data.

3871 reads — 0 comments

You have two options for how to access data that a DataReader receives.

2378 reads — 0 comments

You should never block in a listener callback.  There are many negative consequences of blocking in a listener callback:

5835 reads — 0 comments

A DDS Publisher and Subscriber are responsible for sending and receiving the data. A Publisher contains one or multiple DataWriters.

5362 reads — 0 comments

Pages