dido:public:ra:1.2_views:2_tech_views:2-nodenet:3_nodearch
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
dido:public:ra:1.2_views:2_tech_views:2-nodenet:3_nodearch [2021/09/28 12:18] 50.19.247.197 ↷ Links adapted because of a move operation |
dido:public:ra:1.2_views:2_tech_views:2-nodenet:3_nodearch [2022/02/03 20:35] (current) 52.45.51.99 ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 14: | Line 14: | ||
| </figure> | </figure> | ||
| - | The DIDO node component model presented in this diagram (Figure {{ref>NCModel}}) may look like a traditional stack or layered architecture as described in centralized or decentralized models; however, a very important difference is that the components or a subset of the components of this architecture are usually repeated at every DIDO node that participates in the DIDO network. At a minimum, the secure message and the distribution software components must exist at each node in order for the network to remain distributed and operational. In addition to providing for the core components required to securely communicate, a DIDO node can take on different roles or functions (refer to Figure {{ref>DIDONodes}}). Some nodes may use all the components within the DIDO node component model while others may only use a subset of these components. For example, a [[dido:public:ra:xapend:xapend.a_glossary:s:smart_contracts|smart contract]] node may use the identity, transaction, [[dido:public:ra:xapend:xapend.a_glossary:l:ledger|ledger]], distributed app, and ancillary data components. In contrast, a Wallet node may just use wallet and identity components. | + | The DIDO node component model presented in this diagram (Figure {{ref>NCModel}}) may look like a traditional stack or layered architecture as described in centralized or decentralized models; however, a very important difference is that the components or a subset of the components of this architecture are usually repeated at every DIDO node that participates in the DIDO network. At a minimum, the secure message and the distribution software components must exist at each node in order for the network to remain distributed and operational. In addition to providing for the core components required to securely communicate, a DIDO node can take on different roles or functions (refer to Figure {{ref>DIDONodes}}). Some nodes may use all the components within the DIDO node component model while others may only use a subset of these components. For example, a [[dido:public:ra:xapend:xapend.a_glossary:s:smart_contract|smart contract]] node may use the identity, transaction, [[dido:public:ra:xapend:xapend.a_glossary:l:ledger|ledger]], distributed app, and ancillary data components. In contrast, a Wallet node may just use wallet and identity components. |
| <figure DIDONodes> | <figure DIDONodes> | ||
dido/public/ra/1.2_views/2_tech_views/2-nodenet/3_nodearch.1632845913.txt.gz · Last modified: 2021/09/28 12:18 by 50.19.247.197
