dido:public:ra:1.4_req:2_nonfunc:14_reliability:04_faulttolerance
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:1.4_req:2_nonfunc:14_reliability:04_faulttolerance [2021/07/26 14:00] murphy [About] |
dido:public:ra:1.4_req:2_nonfunc:14_reliability:04_faulttolerance [2021/08/11 13:25] (current) murphy |
||
|---|---|---|---|
| Line 14: | Line 14: | ||
| * **Power sources** are ruggedized as fault tolerant by incorporating alternative sources and backups like [[dido:public:ra:xapend:xapend.a_glossary:u:ups]] and backup generators. A good description of this is provided in the [[https://www.omgwiki.org/ddsf/doku.php?id=ddsf:private:cookbook:03_user:03_tms | Tactical Microgrid Standard (TMS) ]] [[dido:public:ra:xapend:xapend.a_glossary:u:use_case|use case]], | * **Power sources** are ruggedized as fault tolerant by incorporating alternative sources and backups like [[dido:public:ra:xapend:xapend.a_glossary:u:ups]] and backup generators. A good description of this is provided in the [[https://www.omgwiki.org/ddsf/doku.php?id=ddsf:private:cookbook:03_user:03_tms | Tactical Microgrid Standard (TMS) ]] [[dido:public:ra:xapend:xapend.a_glossary:u:use_case|use case]], | ||
| * **Hardware systems** are made Fault Tolerant by deploying identical or equivalent systems that can either be used instead of the original system or use in conjunctions with the original system used as an alternative. For example, a [[dido:public:ra:xapend:xapend.a_glossary:s:server|server]] can be made fault tolerant by using an identical server running in parallel, with all operations mirrored to the backup server. | * **Hardware systems** are made Fault Tolerant by deploying identical or equivalent systems that can either be used instead of the original system or use in conjunctions with the original system used as an alternative. For example, a [[dido:public:ra:xapend:xapend.a_glossary:s:server|server]] can be made fault tolerant by using an identical server running in parallel, with all operations mirrored to the backup server. | ||
| - | * **Networks** designed as Fault Tolerant by supporting multiple networks paths between any two [[dido:public:ra:xapend:xapend.a_glossary:e:endpoint|endpoints]] within the [[dido:public:ra:xapend:xapend.a_glossary:l:lan]] or [[dido:public:ra:xapend:xapend.a_glossary:w:wan]] are possible but the actual endpoint also needs to be duplicated (i.e., two Network Interface Cards (NICs)). It is also possible to use two different networks such as a [[dido:public:ra:xapend:xapend.a_glossary:w:wired | wired]], [[dido:public:ra:xapend:xapend.a_glossary:w:wifi]], [[dido:public:ra:xapend:xapend.a_glossary:b:bluetooth]], or [[dido:public:ra:xapend:xapend.a_glossary:z:zigbee]]. | + | * **Networks** designed as Fault Tolerant by supporting multiple networks paths between any two [[dido:public:ra:xapend:xapend.a_glossary:e:endpoint|endpoints]] within the [[dido:public:ra:xapend:xapend.a_glossary:l:lan]] or [[dido:public:ra:xapend:xapend.a_glossary:w:wan]] are possible but the actual endpoint also needs to be duplicated (i.e., two Network [[dido:public:ra:xapend:xapend.a_glossary:i:interface|Interface]] Cards (NICs)). It is also possible to use two different networks such as a [[dido:public:ra:xapend:xapend.a_glossary:w:wired | wired]], [[dido:public:ra:xapend:xapend.a_glossary:w:wifi]], [[dido:public:ra:xapend:xapend.a_glossary:b:bluetooth]], or [[dido:public:ra:xapend:xapend.a_glossary:z:zigbee]]. |
| - | * **Software** systems or components become fault tolerant when multiple instances of the software are running in parallel using either operating system threads or even more modern [[dido:public:ra:xapend:xapend.a_glossary:c:container|containers]] such as [[dido:public:ra:xapend:xapend.a_glossary:d:docker]] or orchestration software such as [[https://kubernetes.io/ | Kubernetes]]. For example, a database can be continuously replicated to other machines. If the primary database goes down, operations can be automatically redirected to the second database. Another example, would be use of orchestration software such as Kubernetes to automatically use an alternate [[dido:public:ra:xapend:xapend.a_glossary:a:application_binary_interface_api|application container]] on the same or different machine. | + | * **Software** systems or components become fault tolerant when multiple instances of the software are running in parallel using either [[dido:public:ra:xapend:xapend.a_glossary:o:os|operating system]] threads or even more modern [[dido:public:ra:xapend:xapend.a_glossary:c:container|containers]] such as [[dido:public:ra:xapend:xapend.a_glossary:d:docker]] or orchestration software such as [[https://kubernetes.io/ | Kubernetes]]. For example, a database can be continuously replicated to other machines. If the primary database goes down, operations can be automatically redirected to the second database. Another example, would be use of orchestration software such as Kubernetes to automatically use an alternate [[dido:public:ra:xapend:xapend.a_glossary:a:app_container|application container]] on the same or different machine. |
| | | ||
dido/public/ra/1.4_req/2_nonfunc/14_reliability/04_faulttolerance.1627322420.txt.gz · Last modified: 2021/07/26 14:00 by murphy
