public:99_annexes:annex-b-terms-and-definitions:n:node_definition

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:99_annexes:annex-b-terms-and-definitions:n:node_definition [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:n:node_definition [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Node Implementation ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +A Node Implementation realizes a [[public:99_annexes:annex-b-terms-and-definitions:n:node_definition|Node Definition]] through executable and supporting artifacts.
 +
 +The artifacts include executable code, generated code, libraries, container images, machine images, scripts, schemas, interface definitions, deployment descriptors, and other implementation content required to instantiate the [[public:99_annexes:annex-b-terms-and-definitions:n:node|Node]].
 +
 +A Node Implementation remains distinct from a [[public:99_annexes:annex-b-terms-and-definitions:n:node_configuration|Node Configuration]]. The Node Implementation supplies the implemented capabilities and behavior. The Node Configuration supplies the values, settings, bindings, and policies applied to a particular Node instance.
 +
 +A Node Implementation also remains distinct from a Node instance. The Node Implementation constitutes reusable implementation content. A Node instance constitutes an individually identifiable realization produced from the implementation and its applied configuration within a deployment or [[public:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]].
 +
 +===== Definition =====
 +
 +//realization of a Node Definition as executable and supporting artifacts//
 +
 +===== Source =====
 +
 +DIDO Solutions project definition.
 +
 +===== Note =====
 +
 +One Node Definition has multiple Node Implementations when different technologies, platforms, products, programming languages, or deployment mechanisms realize the same specified characteristics.
 +
 +One Node Implementation produces multiple Node instances through separate deployment and configuration activities.
 +
 +A Node Implementation identifies its version, constituent artifacts, dependencies, build provenance, integrity information, applicable Node Definition, and conformance status.
 +
 +A change to executable or supporting implementation content produces a distinguishable Node Implementation revision. A change limited to Configuration Values produces a Node Configuration revision rather than a Node Implementation revision.
 +
 +===== Example =====
 +
 +A container image containing a market-data publisher executable, its required libraries, interface definitions, startup scripts, and deployment descriptors constitutes a Node Implementation. Applying endpoint addresses, credentials, topic names, and runtime limits creates a Node Configuration for a particular Node instance.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>