10.1 Overview [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 10.1 Overview ======
[[fxdemo:02-part:start | Go To Top ]]

Logical Interaction Patterns define recurring platform-independent patterns of cooperation among [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Nodes]].

Each pattern identifies the participating [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Nodes]] or [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_role|Logical Node Roles]], the [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Logical Communication Endpoints]] involved, the [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_structure_instance|Logical Data Structure Instances]] exchanged or recorded, the Logical Runtime Plane that frames the interaction, and the [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] or [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] expectations that support review.

The Logical Interaction Patterns do not prescribe DDS, REST, RPC, Protocol Buffers, message queues, event streams, file exchange, shared services, databases, logs, or deployment mechanisms. Implementation profiles select the technologies and runtime mechanisms that realize these patterns.

The patterns in this section provide a reusable logical vocabulary for later domain profiles. A domain profile specializes these patterns for a specific financial Domain while preserving the platform-independent logical architecture.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>