This article was originally published on bmf-tech.com.
Overview
Sometimes it gets confusing, so here's a glossary as a memo.
Terms
Fail-safe
A mechanism that transitions to a safe state when a failure occurs.
Failover
A mechanism that automatically transfers functions to an alternative system and continues processing when a failure occurs in the operating system.
Failback
The process of transferring operations back from an alternative system to the original system, restoring it to its original state. The opposite of failover.
Fail-soft
Continuing operation by removing the faulty part and narrowing the impact range when a failure occurs.
Fault-tolerant
Maintaining normal operation by switching to an alternative system when a failure occurs.
Fault Avoidance
The concept of eliminating factors that cause system failures or malfunctions to prevent them from occurring.
Fallback
Maintaining system availability by limiting functions or performance, or switching to another system when a failure occurs. Also known as degraded operation.
Foolproof
Designing a system so that users cannot perform incorrect operations or use it in dangerous ways. Also refers to such mechanisms or structures.
Fault Masking
Creating a mechanism that prevents the spread of impact even if a failure occurs.
Thoughts
There was an article with similar sentiments.
zenn.dev - Confusing Technical Terms: Fail〇〇, Fault〇〇
qiita.com - Differences between Fault-tolerant, Fail-soft, and others
Top comments (0)