===== 20.2 DDS Vendor Decisions =====

[[fxdemo:05-part:start | Go To Top ]]

[[fxdemo:05-part:20-risks-and-open-decisions:start | Return to Risks and Open Decisions ]]

The team must decide which DDS product or products Phase 0 uses. The initial baseline may use one primary DDS product, while later phases may add supported alternatives or interoperability targets.

Open DDS decisions may include:

  - Which DDS product acts as the primary baseline.
  - Whether Phase 0 supports RTI Connext DDS, Eclipse Cyclone DDS, OpenDDS, or another DDS implementation.
  - Which DDS version range the team accepts for each product.
  - Which IDL compiler or type-generation tool the team uses.
  - Which target language bindings the team generates.
  - Which QoS features Phase 0 requires.
  - Whether Phase 0 includes single-vendor operation, multi-vendor build compatibility, multi-vendor runtime interoperability, or only future interoperability planning.

DDS decisions affect IDL structure, generated [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]], QoS configuration, build scripts, container networking, runtime behavior, interoperability Evidence, and developer setup. The team should record product selections, version ranges, interoperability status, and Evidence expectations in the tool baseline checklist instance.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>