15.5 FX Execution and Deployment Independence [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.

====== 15.5 FX Execution and Deployment Independence ======
[[fxdemo:03-part:15-relationship-to-implementation-profiles-psm:start | Go To Relationship to Implementation Profiles / PSM ]]

The FX Demo Logical Profile does not prescribe execution granularity, deployment granularity, runtime packaging, orchestration, hosting, or operational topology.

An Implementation Profile / [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model|PSM]] selects execution and packaging mechanisms to realise FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Nodes]] and 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 FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Node]] or logical responsibility. It does not redefine the FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Node]], FX logical Node identity, FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_role|Node Role]], or the FX logical Node boundary.

----

<WRAP centeralign>

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

</WRAP>