fxdemo:02-part:14-relationship-to-implementation-profiles-psm:14-5-execution-and-deployment-independence:start

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
fxdemo:02-part:14-relationship-to-implementation-profiles-psm:14-5-execution-and-deployment-independence:start [2026/07/11 11:07] – ↷ Links adapted because of a move operation nick_didofxdemo:02-part:14-relationship-to-implementation-profiles-psm:14-5-execution-and-deployment-independence:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 4: Line 4:
 The Logical Architecture / PIM does not prescribe execution granularity, deployment granularity, runtime packaging, orchestration, hosting, or operational topology. The Logical Architecture / PIM does not prescribe execution granularity, deployment granularity, runtime packaging, orchestration, hosting, or operational topology.
  
-An Implementation Profile / PSM selects execution and packaging mechanisms to realise [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Nodes]] and logical responsibilities. Those mechanisms include, for example, subroutines, libraries, threads, tasks, processes, services, containers, pods, virtual machines, serverless functions, gateways, external subscribers, or other executable or addressable participants.+An Implementation Profile / PSM selects execution and packaging mechanisms to realize [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Nodes]] and logical responsibilities. Those mechanisms include, for example, subroutines, libraries, threads, tasks, processes, services, containers, pods, virtual machines, serverless functions, gateways, external subscribers, or other executable or addressable participants.
  
-The selected execution mechanism realises the [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] or logical responsibility. It does not redefine the [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]], [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_node_identity|Logical Node Identity]], [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_node_role|Logical Node Role]], or Logical Node Boundary.+The selected execution mechanism realizes the [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] or logical responsibility. It does not redefine the [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_identity|Logical Node Identity]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_role|Logical Node Role]], or Logical Node Boundary.
  
 ---- ----
  • fxdemo/02-part/14-relationship-to-implementation-profiles-psm/14-5-execution-and-deployment-independence/start.1783793243.txt.gz
  • Last modified: 2026/07/11 11:07
  • by nick_dido