Differences

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

--- fxdemo:01-part:11-conceptual-rules-and-constraints:11-3-conceptual-architecture-does-not-prescribe-realisation-mechanisms [2026/07/11 11:07] – ↷ Links adapted because of a move operation nick_dido
+++ fxdemo:01-part:11-conceptual-rules-and-constraints:11-3-conceptual-architecture-does-not-prescribe-realisation-mechanisms [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
-====== 11.3 Conceptual Architecture Does Not Prescribe Realisation Mechanisms ======
+====== 11.3 Conceptual Architecture Does Not Prescribe Realization Mechanisms ======
 [[fxdemo:01-part:start | Go to Top ]]
-The Conceptual Architecture defines architectural responsibilities and relationships. It does not prescribe execution granularity, deployment granularity, communication technology, interface style, [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:d:data|Data]] serialisation format, or runtime packaging.
+The Conceptual Architecture defines architectural responsibilities and relationships. It does not prescribe execution granularity, deployment granularity, communication technology, interface style, [[dido:99_annexes:annex-b-terms-and-definitions:d:data|Data]] serialisation format, or runtime packaging.
-A later part may realise a [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:n:node|Node]] as a subroutine, library component, thread, task, process, service, container, pod, virtual machine, serverless function, RPC endpoint, gateway, external subscriber, or other executable or addressable participant. Those realisations do not redefine the concept of [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:n:node|Node]].
+A later part may realize a [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] as a subroutine, library component, thread, task, process, service, container, pod, virtual machine, serverless function, RPC endpoint, gateway, external subscriber, or other executable or addressable participant. Those realisations do not redefine the concept of [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]].
-A later part may realise a [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]] through publish/subscribe, request/response, RPC, REST, message queues, event streams, file exchange, shared memory, database handoff, gateway access, service invocation, or another exchange mechanism. Those realisations do not redefine the concept of [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]].
+A later part may realize a [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]] through publish/subscribe, request/response, RPC, REST, message queues, event streams, file exchange, shared memory, database handoff, gateway access, service invocation, or another exchange mechanism. Those realisations do not redefine the concept of [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]].
-A later part may realise a [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]] through IDL, Protocol Buffers, JSON Schema, XML Schema, Avro, OpenAPI schemas, UML, SysML, ontology classes, database schemas, generated language types, or another formal representation. Those realisations do not redefine the concept of [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]].
+A later part may realize a [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]] through IDL, Protocol Buffers, JSON Schema, XML Schema, Avro, OpenAPI schemas, UML, SysML, ontology classes, database schemas, generated language types, or another formal representation. Those realisations do not redefine the concept of [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]].
-A later part may realise modular development through libraries, services, processes, containers, orchestrated workloads, RPC services, REST resources, event-driven components, or other implementation structures. Those choices remain implementation or deployment decisions. They do not define the conceptual architecture.
+A later part may realize modular development through libraries, services, processes, containers, orchestrated workloads, RPC services, REST resources, event-driven components, or other implementation structures. Those choices remain implementation or deployment decisions. They do not define the conceptual architecture.
 ----