Control Plane

Return to Terms and Definitions

Discussion

The Control Plane supports operational coordination among Nodes. It allows the architecture to manage registration, capability advertisement, health reporting, command handling, configuration coordination, schema and model version coordination, work assignment, retries, recovery, replay, and other runtime management concerns.

The Control Plane does not normally carry domain truth. It coordinates how Nodes operate, but it does not replace the Data Plane, Policy and Release Plane, Health and Observability Plane, or Audit and Provenance Plane.

A later implementation profile may realize Control Plane interactions through DDS Topics, service interfaces, message queues, APIs, configuration channels, or other runtime mechanisms. Those mechanisms do not redefine the Control Plane.

Definition

Runtime Plane supporting operational coordination among Nodes

Source

Adapted from FX Demo Reference Architecture, Section 2.1.13, Control Plane, and Section 4.4.3, Control Plane; generalised from DDS-specific control-plane usage to the Financial Systems Archetype conceptual layer.

Note

The Control Plane is not a DDS Domain, a DDS Topic, a Kubernetes namespace, a configuration file, a command protocol, or a deployment environment.

Example

A command requesting a Node to report status, reload configuration, retry work, or initiate recovery may belong to the Control Plane.