====== 16.2 FX Logical Nodes Remain Distinct from Runtime Deployments ====== [[fxdemo:03-part:16-fx-demo-logical-rules-and-constraints:start | Go To FX Demo Logical Rules and Constraints ]] An FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Node]] represents a platform-independent participant in the FX Demo Logical Profile. It does not represent a process, service, container, pod, virtual machine, serverless function, thread, task, library, subroutine, [[dido:99_annexes:annex-b-terms-and-definitions:r:rpc|RPC]] endpoint, [[dido:99_annexes:annex-b-terms-and-definitions:r:rest|REST]] resource, [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] participant, or deployment artefact. Implementation profiles select execution mechanisms that realise FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Nodes]]. Deployment profiles then describe how those implementation artefacts run in a concrete environment. A single runtime artefact implements several FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Nodes]] when the selected implementation approach combines responsibilities. Several runtime artefacts implement one FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Node]] when the selected implementation approach distributes responsibility. Neither choice redefines the FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Node]]. ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.