====== 15.2 Logical Nodes Remain Distinct from Runtime Deployments ====== [[fxdemo:02-part:start | Go To Top ]] A [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] represents a platform-independent participant in the logical architecture. It does not represent a process, service, container, pod, virtual machine, serverless function, thread, task, library, subroutine, RPC endpoint, REST resource, DDS participant, or deployment artifact. Implementation profiles select execution mechanisms that realize [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Nodes]]. Deployment profiles then describe how those implementation artifacts run in a concrete environment. A single runtime artifact implements several [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Nodes]] when the selected implementation approach combines responsibilities. Several runtime artifacts implement a single [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] when the selected implementation approach distributes responsibility. Neither choice redefines the [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]]. ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.