dido:99_annexes:annex-b-terms-and-definitions:n:node_role

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:99_annexes:annex-b-terms-and-definitions:n:node_role [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-b-terms-and-definitions:n:node_role [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Node Role ======
  
 +[[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +A Node Role identifies the responsibility a [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] performs within the architecture. Node Roles allow the architecture to describe what a Node does without binding that responsibility to a specific technology, process, container, pod, or deployment unit.
 +A Node may perform one Node Role or multiple Node Roles. A logical architecture may keep several roles together within a single Node. At the same time, a later implementation or deployment profile may separate those roles across multiple Nodes for scaling, resilience, governance, jurisdictional separation, or operational control.
 +Node Roles support traceability by connecting architectural responsibility to logical design, implementation artifacts, deployment artifacts, and evidence.
 +
 +===== Definition =====
 +
 +//responsibility performed by a [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] within the architecture//
 +
 +===== Source =====
 +
 +Adapted from FX Demo Reference Architecture, Section 10, Node Role Framework; generalised for use in the Financial Systems Archetype conceptual layer.
 +
 +===== Note =====
 +
 +A Node Role is not itself a deployed participant. A [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] performs a Node Role.
 +
 +===== Example =====
 +
 +Examples of Node Roles include service registration, health monitoring, transaction intake, validation, attestation, policy evaluation, release control, persistence, replay, audit recording, and provenance recording.