6.1 Overview [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 6.1 Overview ======
[[fxdemo:02-part:start | Go To Top ]]

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 [[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 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.
  Logical Node
  ├── has Logical Node Identity
  ├── performs Logical Node Role
  ├── has Logical Node Responsibility
  ├── participates in Logical Runtime Plane
  ├── uses Logical Communication Endpoint
  └── participates in Logical Interaction
Figure 6-1:	Primary relationships in the Logical Node Model


----

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