Differences

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

--- fxdemo:02-part:05-logical-architecture-overview:05-1-overview:start [2026/07/11 11:07] – ↷ Links adapted because of a move operation nick_dido
+++ fxdemo:02-part:05-logical-architecture-overview:05-1-overview:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 2: / Line 2: @@
 [[fxdemo:02-part:start | Go To Top ]]
-The distributed, node-based Logical Architecture / PIM defines a single platform-independent way to realise the Part 1 Conceptual Architecture at the logical level.
+The distributed, node-based Logical Architecture / PIM defines a single platform-independent way to realize the Part 1 Conceptual Architecture at the logical level.
-This Logical Architecture organises a financial, structured information-processing system as a network of identifiable logical Nodes. Each logical Node performs one or more logical [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_node_role|Node Roles]], participates in one or more logical Runtime Planes, and communicates with other logical Nodes through explicit logical [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Communication Endpoints]].
+This Logical Architecture organizes a financial, structured information-processing system as a network of identifiable logical Nodes. Each logical Node performs one or more logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_role|Node Roles]], participates in one or more logical Runtime Planes, and communicates with other logical Nodes through explicit logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Communication Endpoints]].
-The Logical Architecture / PIM does not prescribe a technology stack, protocol, data serialisation format, programming language, deployment topology, or runtime packaging. Implementation profiles realise this Logical Architecture through selected mechanisms such as DDS, REST, RPC, Protocol Buffers, message queues, event streams, file exchange, shared services, libraries, threads, tasks, processes, containers, virtual machines, or other mechanisms.
+The Logical Architecture / PIM does not prescribe a technology stack, protocol, data serialisation format, programming language, deployment topology, or runtime packaging. Implementation profiles realize this Logical Architecture through selected mechanisms such as DDS, REST, RPC, Protocol Buffers, message queues, event streams, file exchange, shared services, libraries, threads, tasks, processes, containers, virtual machines, or other mechanisms.
 Figure 5-1 summarises the high-level structure of the distributed, node-based Logical Architecture / PIM.