This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |
| dido:99_annexes:annex-b-terms-and-definitions:d:dds [2026/08/04 07:08] – ↷ Links adapted because of a move operation nick_dido | dido:99_annexes:annex-b-terms-and-definitions:d:dds [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido |
|---|
| Data Distribution Service (DDS) is a standards-based middleware technology for data-centric publish-subscribe communication. | Data Distribution Service (DDS) is a standards-based middleware technology for data-centric publish-subscribe communication. |
| |
| In the Financial Systems [[dido:99_annexes:annex-b-terms-and-definitions:a:archetype|Archetype]] document set, DDS falls under implementation and platform-specific mapping concerns. DDS does not define the logical architecture, logical [[dido:99_annexes:annex-b-terms-and-definitions:n:financial_node|Nodes]], logical [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoints]], logical information structures, logical [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]], or logical interaction patterns. Those concepts belong to the Logical Architecture / [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|PIM]] and to domain logical profiles. | In the Financial Systems [[dido:99_annexes:annex-b-terms-and-definitions:a:archetype|Archetype]] document set, DDS falls under implementation and platform-specific mapping concerns. DDS does not define the logical architecture, logical [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Nodes]], logical [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoints]], logical information structures, logical [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]], or logical interaction patterns. Those concepts belong to the Logical Architecture / [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|PIM]] and to domain logical profiles. |
| |
| An implementation profile maps selected logical Communication Endpoints, logical information structures, and interaction patterns to DDS concepts such as Domain Participants, Topics, DataWriters, DataReaders, Quality of Service policies, partitions, and generated type bindings. | An implementation profile maps selected logical Communication Endpoints, logical information structures, and interaction patterns to DDS concepts such as Domain Participants, Topics, DataWriters, DataReaders, Quality of Service policies, partitions, and generated type bindings. |