Skip to content

    Fault Tolerance

    Web design & developmentInterference tolerance
    Editorially reviewed on: 1 source
    Your reading view

    The short answer · 20 words

    In short

    Fault tolerance enables a system to continue to operate correctly or restricted in a controlled manner despite certain component faults.

    Flow-alerta.cab (2026): Fault Tolerance. https://flow-alerta.cab/en/glossar/fault-tolerance. Editorially reviewed on: 10 October 2026.

    How much detail would you like?

    Practical

    It can limit the effects of defined individual defects and partial failures; common causes of error and restart must be considered.

    Hypothetical example: If an AI service fails, a process switches to manual testing instead of losing data.

    SMEs should define critical dependencies, safe fallbacks, restarts and exercises.

    At a glance

    Core
    Redundancy, isolation, repetition, replication and orderly degradation limit impacts. Fault tolerance is not the same as high availability or disaster recovery.
    Use
    It can limit the effects of defined individual defects and partial failures; common causes of error and restart must be considered.
    Example
    Hypothetical example: If an AI service fails, a process switches to manual testing instead of losing data.
    Limits
    Repeats without idem power; common causes of error; untested backups; silently false results instead of visible degradation.

    In context

    Questions about this term

    Is fault tolerance the same as high availability?

    No.

    Does it mean zero failure?

    No, but dominated behavior.

    All details and background

    Redundancy, isolation, repetition, replication and orderly degradation limit impacts. Fault tolerance is not the same as high availability or disaster recovery.

    ELI5 – Explained simply

    If one part fails, another takes over or the system falls back safely.

    Why it matters in practice

    It can limit the effects of defined individual defects and partial failures; common causes of error and restart must be considered.

    Example

    Hypothetical example: If an AI service fails, a process switches to manual testing instead of losing data.

    Pitfalls and limits

    • Repeats without idem power; common causes of error; untested backups; silently false results instead of visible degradation.

    Origin & history

    Google’s SRE manual documents protection against overload and cascading outages as well as controlled rejection of unprocessable requests.

    Use in mid-sized companies

    • SMEs should define critical dependencies, safe fallbacks, restarts and exercises.

    Sources

    Quellenprüfung: 10.10.2026. Definition und dokumentierte Einordnung abgeglichen; Beispiele beschreiben mögliche Anwendungen.

    Editorially reviewed on:

    Next step

    Put knowledge into practice