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).

Use Modern C++ Types Correctly

To use the Modern C++ Connext DDS API correctly you need to understand its type system. Most types in the API belong into two categories:

- Value types

- Reference types

alexc
Tue, 08/18/2020 - 14:26
4794 reads — 1 comment

Don’t use the same Permissions File for all DomainParticipants

For better performance and reduced network usage, use individual Permissions Files for each

cristiangguerrero
Thu, 08/22/2019 - 10:54
5102 reads — 0 comments

QoS Profile Inheritance and Composition Guidance

QoS Profile composition is a new feature added to Connext DDS 6. This feature allows QoS Profiles to be constructed from other profiles using composition. Learn the details of this feature and how to properly use it.
Pralhad Sapre
Wed, 06/19/2019 - 18:05
49457 reads — 0 comments

Read reference DDS Best Practices Material from RTI

The following references summarize key best practices when using DDS to integrate distributed systems:

Gerardo Pardo
Fri, 04/07/2017 - 06:35
8230 reads — 0 comments

Modern C++ API: Don’t Declare Entities As Pointers

Entities, such as the DomainParticipant or the DataReader should never be created as pointers (i.e. using new). They implement reference semantics, and should be declared as regular variables.
alexc
Tue, 07/07/2015 - 14:15
12957 reads — 0 comments

Configure Your QoS Through Profiles

For better reusability and maintenance of your code, design your QoS as sets of reusable profiles instead of tuning each data flow separately.

rose
Thu, 02/27/2014 - 09:46
12661 reads — 0 comments

Don't Force Topic Names to be the Same as Type Names

Your Topic names should represent the meaning of the data you are sending, not the structure of the data.

rose
Wed, 02/26/2014 - 16:11
23185 reads — 0 comments

Pages