Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:d:distributed_network_topology [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:d:distributed_network_topology [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Distributed Network Topology ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A Distributed Network Topology arranges multiple networked [[public: | ||
| + | |||
| + | The topology distributes network participation across multiple Nodes rather than requiring all communication or coordination to pass through one central Node. | ||
| + | |||
| + | Characteristics of a Distributed Network Topology include: | ||
| + | |||
| + | * Multiple interconnected Nodes | ||
| + | * Direct or indirect communication among participating Nodes | ||
| + | * Distribution of communication, | ||
| + | * Continued communication among remaining Nodes following the loss of a participating Node, when permitted by the governing architecture | ||
| + | * Absence of a single Node through which every network interaction must pass | ||
| + | |||
| + | Participating Nodes do not need to perform identical functions or possess equal authority. | ||
| + | |||
| + | The governing architecture assigns roles and responsibilities such as: | ||
| + | |||
| + | * Producing data | ||
| + | * Consuming data | ||
| + | * Routing messages | ||
| + | * Processing requests | ||
| + | * Storing data | ||
| + | * Replicating data | ||
| + | * Validating transactions | ||
| + | * Coordinating state | ||
| + | * Providing discovery | ||
| + | * Enforcing policy | ||
| + | |||
| + | A Distributed Network Topology differs from a [[private: | ||
| + | |||
| + | A Distributed Network Topology also differs from a [[public: | ||
| + | |||
| + | * A Distributed Network Topology describes the arrangement and interconnection of Nodes | ||
| + | * A Distributed System describes the coordinated system behavior performed across those Nodes | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | * DIDO Reference Architecture, | ||
| + | * DIDO Reference Architecture, | ||
| + | * Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | A Distributed Network Topology does not require every Node to: | ||
| + | |||
| + | * Hold the same data | ||
| + | * Perform the same processing | ||
| + | * Communicate directly with every other Node | ||
| + | * Possess equal authority | ||
| + | * Provide the same services | ||
| + | * Remain continuously available | ||
| + | |||
| + | The governing architecture determines: | ||
| + | |||
| + | * Node roles | ||
| + | * Communication paths | ||
| + | * Routing behavior | ||
| + | * Data distribution | ||
| + | * State coordination | ||
| + | * Redundancy | ||
| + | * Failure handling | ||
| + | * Discovery mechanisms | ||
| + | * Security controls | ||
| + | * Authority relationships | ||
| + | |||
| + | A Distributed Network Topology can contain gateways, coordinators, | ||
| + | |||
| + | The term does not prescribe peer-to-peer protocols, blockchain, distributed ledgers, consensus algorithms, message brokers, cloud computing, or a particular transport protocol. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A deployment-management network contains multiple Nodes that exchange deployment requests, status information, | ||
| + | |||
| + | Execution Nodes perform deployment operations, storage Nodes preserve records, and validation Nodes assess results. The Nodes perform different roles while participating in one Distributed Network Topology. | ||
| + | |||
| + | Loss of one execution Node does not prevent the remaining Nodes from communicating or performing the operations permitted by the governing architecture. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||