12.5 Data Plane QoS Expectations [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== 12.5 Data Plane QoS Expectations ======

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

[[fxdemo:05-part:12-data-plane-topics:start | Return to Data Plane Topics ]]

[[dido:99_annexes:annex-b-terms-and-definitions:d:data_plane|Data Plane]] Topics should use [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] QoS settings that match the meaning and expected behavior of the data they carry. Phase 0 may use simple QoS profiles, but the team should still document the assumptions that affect delivery, ordering, durability, history, liveliness, and replay.

The team should document Data Plane QoS expectations in the Topic Catalogue and DDS Configuration files. When a QoS setting matters to the demonstration, the implementation should not rely on undocumented DDS defaults.

For Data Plane Topics, the team should consider:

  - Reliability.
  - Durability.
  - History depth.
  - Ordering.
  - Liveliness.
  - Lifespan.
  - Deadline.
  - Ownership.
  - Resource limits.
  - Partitioning or domain separation, where applicable.

Phase 0 should keep QoS choices understandable. The team should not introduce complex QoS behavior unless the demonstration requires it. If a QoS choice affects acceptance [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]], publisher/subscriber compatibility, or cross-vendor DDS behavior, the team should record the expectation and validation result.

----

<WRAP centeralign>

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

</WRAP>