====== Data Plane ======

[[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]

===== Discussion =====

The Data Plane carries business-domain, financial, analytical, lifecycle, and derived information exchanged among [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Nodes]]. It supports the movement of information representing events, observations, assertions, computations, state changes, and domain results.

The Data Plane remains distinct from the [[dido:99_annexes:annex-b-terms-and-definitions:c:control_plane|Control Plane]]. The Data Plane carries domain and analytical information. The Control Plane coordinates runtime operation.

A later implementation profile may realize Data Plane interactions through DDS Topics, API endpoints, event streams, message queues, files, or other communication mechanisms. Those mechanisms do not redefine the Data Plane.

===== Definition =====

//[[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] carrying domain and analytical information among [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Nodes]]//

===== Source =====

Adapted from FX Demo Reference Architecture, Section 2.1.12, Data Plane, and Section 4.4.2, Data Plane; generalised from DDS-specific data-plane usage to the Financial Systems Archetype conceptual layer.

===== Note =====

The Data Plane is not a persistence mechanism, a database, a DDS Domain, a DDS Topic, or a network segment.

===== Example =====

An FX transaction event, cash-flow obligation, validation result, analytical assertion, or lifecycle state change may belong to the Data Plane.
----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>