This is an old revision of the document!


15.2 Logical Nodes Remain Distinct from Runtime Deployments

Go To Top

A 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 artefact.

Implementation profiles select execution mechanisms that realise Logical Nodes. Deployment profiles then describe how those implementation artefacts run in a concrete environment.

A single runtime artefact implements several Logical Nodes when the selected implementation approach combines responsibilities. Several runtime artefacts implement a single Logical Node when the selected implementation approach distributes responsibility. Neither choice redefines the Logical Node.


© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

  • fxdemo/02-part/15-logical-rules-and-constraints/15-2-logical-nodes-remain-distinct-from-runtime-deployments/start.1783793724.txt.gz
  • Last modified: 2026/07/11 11:15
  • by nick_dido