Differences

This shows you the differences between two versions of the page.

--- dido:99_annexes:annex-b-terms-and-definitions:d:dds [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1
+++ 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
@@ Line 1: / Line 1: @@
+====== Data Distribution Service (DDS) ======
+[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
+===== Discussion =====
+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: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.
+===== Definition =====
+//standards-based middleware technology for data-centric publish-subscribe communication among distributed software participants//
+===== Source =====
+Generalised from the Object Management Group Data Distribution Service specification and its use as an implementation mapping technology in [[fxdemo:04-part:start]].
+===== Note =====
+DDS is not a Runtime Plane, logical Communication Endpoint, logical Node, logical information structure, message bus, database, deployment environment, or governance model.
+===== Example =====
+[[fxdemo:04-part:start]] maps selected FX Demo logical Communication Endpoints and logical information structures to DDS Topics, DataWriters, DataReaders, Quality of Service policies, and generated type bindings.
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>