====== 15.8 Logical Architecture Does Not Prescribe Communication Pattern Implementation ====== [[fxdemo:02-part:start | Go To Top ]] The Logical Architecture / PIM defines communication roles and interaction patterns without prescribing how a selected technology implements them. A logical publication does not require DDS or an event stream. A logical subscription does not require topic-based middleware. A logical request does not require REST or RPC. A logical command does not require an orchestration command or control API. A logical acknowledgement does not require synchronous communication. Implementation profiles select communication patterns and technologies that realize the logical interaction while preserving logical meaning, [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], Runtime Plane classification, governance constraints, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] expectations. ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.