This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |
| fxdemo:01-part:05-conceptual-architecture-principles:05-4-logical-meaning-before-physical-realisation [2026/08/04 07:08] – ↷ Links adapted because of a move operation nick_dido | fxdemo:01-part:05-conceptual-architecture-principles:05-4-logical-meaning-before-physical-realisation [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido |
|---|
| The architecture defines logical meaning before physical realization. | The architecture defines logical meaning before physical realization. |
| |
| A [[dido:99_annexes:annex-b-terms-and-definitions:n:financial_node|Node]] has a [[dido:99_annexes:annex-b-terms-and-definitions:n:node_role|Node Role]] and [[dido:99_annexes:annex-b-terms-and-definitions:n:node_identity|Node Identity]] before an implementation profile decides whether it runs as a process, container, pod, virtual machine, or service. A [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] serves an architectural purpose, while an implementation profile decides whether to represent it through topic naming, DDS partitions, Kubernetes namespaces, network segmentation, or security policy. | A [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] has a [[dido:99_annexes:annex-b-terms-and-definitions:n:node_role|Node Role]] and [[dido:99_annexes:annex-b-terms-and-definitions:n:node_identity|Node Identity]] before an implementation profile decides whether it runs as a process, container, pod, virtual machine, or service. A [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] serves an architectural purpose, while an implementation profile decides whether to represent it through topic naming, DDS partitions, Kubernetes namespaces, network segmentation, or security policy. |
| |
| ---- | ---- |