dido:public:ra:1.2_views:1_stakeholder
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
dido:public:ra:1.2_views:1_stakeholder [2021/08/18 10:14] murphy |
dido:public:ra:1.2_views:1_stakeholder [2022/01/15 18:23] (current) nick |
||
|---|---|---|---|
| Line 16: | Line 16: | ||
| In contrast to [[dido:public:ra:xapend:xapend.a_glossary:d:distsystem|distributed systems]], centralized systems (i.e., mainframes) are the authority for computation and data. In essence, the only reality is the processes and data that reside in the centralized system. | In contrast to [[dido:public:ra:xapend:xapend.a_glossary:d:distsystem|distributed systems]], centralized systems (i.e., mainframes) are the authority for computation and data. In essence, the only reality is the processes and data that reside in the centralized system. | ||
| - | This is also in contrast to decentralized systems (i.e., traditional cloud servers), which rely on well-orchestrated and coordinated efforts of a few well connected and synchronized systems. Collective servers are the authority for the computation and data. In essence, the only reality is that which can be found on the decentralized servers; the infrastructure is expected to keep the software and data consistent and synchronized. However, this only needs to be concerned with servers that, although they are decentralized, still fall under a single authority thereby making the requirements, architecture, design, implementation, and maintenance relatively easy. | + | This is also in contrast to decentralized systems (i.e., traditional cloud servers), which rely on well-orchestrated and coordinated efforts of a few well-connected and synchronized systems. Collective servers are the authority for the computation and data. In essence, the only reality is that which can be found on the decentralized servers; the infrastructure is expected to keep the software and data consistent and synchronized. However, this only needs to be concerned with servers that, although they are decentralized, still fall under a single authority thereby making the requirements, architecture, design, implementation, and maintenance relatively easy. |
| - | Both centralized and decentralized systems often have extensive data models and functionality, which adds to the complexity of managing them. This generally requires a single governing body (i.e., enterprise) to be ultimately responsible for the entire ecosystem and the lifecycle of the systems and the integration of components including hardware, [[dido:public:ra:xapend:xapend.a_glossary:o:os|operating systems]], [[dido:public:ra:xapend:xapend.a_glossary:d:dbms|database management systems]], web servers, application servers, software languages, networking, and other protocols. These “stacks” often result in stovepipe solutions. | + | Both centralized and decentralized systems often have extensive data models and functionality, which adds to the complexity of managing them. This generally requires a single [[dido:public:ra:xapend:xapend.a_glossary:g:gov_body]] (i.e., enterprise) to be ultimately responsible for the entire ecosystem and the lifecycle of the systems and the integration of components including hardware, [[dido:public:ra:xapend:xapend.a_glossary:o:os|operating systems]], [[dido:public:ra:xapend:xapend.a_glossary:d:dbms|database management systems]], web servers, application servers, software languages, networking, and other protocols. These “stacks” frequently result in stovepipe solutions. |
| In distributed systems, much of the ecosystem and governance of the components is handled by various [[dido:public:ra:xapend:xapend.a_glossary:c:coi| Communities of Interest (CoIs)]]: each has a responsibility for different aspects of the distributed system. The traditional role of a corporation or enterprise is to participate in these communities. The following graphic illustrates the various communities considered to be "customers" of the DIDO RA. | In distributed systems, much of the ecosystem and governance of the components is handled by various [[dido:public:ra:xapend:xapend.a_glossary:c:coi| Communities of Interest (CoIs)]]: each has a responsibility for different aspects of the distributed system. The traditional role of a corporation or enterprise is to participate in these communities. The following graphic illustrates the various communities considered to be "customers" of the DIDO RA. | ||
dido/public/ra/1.2_views/1_stakeholder.1629296057.txt.gz · Last modified: 2021/08/18 10:14 by murphy
