| Both sides previous revision Previous revision | |
| fxdemo:03-part:04-fx-demo-logical-profile-principles:04-3-distributed-fx-node-network:start [2026/08/04 07:08] – ↷ Links adapted because of a move operation nick_dido | fxdemo:03-part:04-fx-demo-logical-profile-principles:04-3-distributed-fx-node-network:start [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido |
|---|
| Each FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Node]] performs one or more FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_role|Node Roles]], participates in one or more FX [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]], communicates through explicit FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Communication Endpoints]], and handles FX logical information structures. | Each FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Node]] performs one or more FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_role|Node Roles]], participates in one or more FX [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]], communicates through explicit FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Communication Endpoints]], and handles FX logical information structures. |
| |
| The distributed FX [[dido:99_annexes:annex-b-terms-and-definitions:n:financial_node|Node]] network supports separation of responsibilities. Transaction intake, validation, semantic interpretation, contract state management, cash-flow computation, policy and release, audit and provenance, health and observability, registry and coordination, replay and reconstruction, and oversight consumption remain distinguishable at the logical level. | The distributed FX [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] network supports separation of responsibilities. Transaction intake, validation, semantic interpretation, contract state management, cash-flow computation, policy and release, audit and provenance, health and observability, registry and coordination, replay and reconstruction, and oversight consumption remain distinguishable at the logical level. |
| |
| This logical distribution does not prescribe separate machines, processes, services, containers, pods, threads, tasks, or deployment units. Implementation and deployment profiles select those realization mechanisms. | This logical distribution does not prescribe separate machines, processes, services, containers, pods, threads, tasks, or deployment units. Implementation and deployment profiles select those realization mechanisms. |