Differences

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

--- fxdemo:02-part:06-logical-node-model:06-1-overview:start [2026/07/11 11:07] – ↷ Links adapted because of a move operation nick_dido
+++ fxdemo:02-part:06-logical-node-model:06-1-overview:start [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 2: / Line 2: @@
 [[fxdemo:02-part:start | Go To Top ]]
-The Logical Node Model specialises the Part 1 concept of [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:n:node|Node]] into a platform-independent logical participant in the distributed, node-based Logical Architecture / PIM.
+The Logical Node Model specializes the Part 1 concept of [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] into a platform-independent logical participant in the distributed, node-based Logical Architecture / PIM.
-A Logical Node represents a separately identifiable participant in the logical architecture. It performs one or more logical [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_node_role|Node Roles]], has a [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_node_identity|Logical Node Identity]], participates in one or more logical Runtime Planes, and communicates through one or more logical [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Communication Endpoints]].
+A Logical Node represents a separately identifiable participant in the logical architecture. It performs one or more logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_role|Node Roles]], has a [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_identity|Logical Node Identity]], participates in one or more logical Runtime Planes, and communicates through one or more logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Communication Endpoints]].
-The Logical Node Model does not prescribe execution or deployment granularity. Implementation profiles select realisation mechanisms for Logical Nodes, such as subroutines, library components, threads, tasks, processes, services, containers, pods, virtual machines, serverless functions, RPC endpoints, gateways, external subscribers, or other executable or addressable participants. Those realisations do not redefine the Logical Node.
+The Logical Node Model does not prescribe execution or deployment granularity. Implementation profiles select realization mechanisms for Logical Nodes, such as subroutines, library components, threads, tasks, processes, services, containers, pods, virtual machines, serverless functions, RPC endpoints, gateways, external subscribers, or other executable or addressable participants. Those realisations do not redefine the Logical Node.
 Figure 6-1 summarises the primary relationships in the Logical Node Model.