fxdemo:02-part:09-logical-runtime-plane-model:09-1-overview:start

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
fxdemo:02-part:09-logical-runtime-plane-model:09-1-overview:start [2026/07/11 11:15] – ↷ Links adapted because of a move operation nick_didofxdemo:02-part:09-logical-runtime-plane-model:09-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 ]] [[fxdemo:02-part:start | Go To Top ]]
  
-The Logical Runtime Plane Model specialises the Part 1 [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] concept into platform-independent logical planes for the distributed, node-based Logical Architecture / PIM.+The Logical Runtime Plane Model specializes the Part 1 [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] concept into platform-independent logical planes for the distributed, node-based Logical Architecture / PIM.
  
 Logical Runtime Planes classify logical interactions by architectural purpose. They help authors and reviewers distinguish operational coordination, domain information exchange, health reporting, policy-governed release, and audit/provenance activity before implementation profiles select communication technologies, deployment mechanisms, or runtime infrastructure. Logical Runtime Planes classify logical interactions by architectural purpose. They help authors and reviewers distinguish operational coordination, domain information exchange, health reporting, policy-governed release, and audit/provenance activity before implementation profiles select communication technologies, deployment mechanisms, or runtime infrastructure.
  
-The Logical Runtime Plane Model does not prescribe DDS domains, DDS topics, DDS partitions, REST resource groups, RPC services, message queues, event streams, Kubernetes namespaces, network segments, security zones, or deployment environments. Implementation profiles select mechanisms to realise logical plane separation, depending on the chosen implementation approach.+The Logical Runtime Plane Model does not prescribe DDS domains, DDS topics, DDS partitions, REST resource groups, RPC services, message queues, event streams, Kubernetes namespaces, network segments, security zones, or deployment environments. Implementation profiles select mechanisms to realize logical plane separation, depending on the chosen implementation approach.
  
 Figure 9-1 summarises the Logical Runtime Plane Model. Figure 9-1 summarises the Logical Runtime Plane Model.
  • fxdemo/02-part/09-logical-runtime-plane-model/09-1-overview/start.1783793712.txt.gz
  • Last modified: 2026/07/11 11:15
  • by nick_dido