Resilience

As explained in Go in Practice, Second Edition

Fault tolerance is the ability of a system to continue operating or recover when components or operations fail.

How Go in Practice, Second Edition covers it

How deep it goes

Classifies several timeout forms and implements bounded recursive retries with resumable downloads, without covering broader failure policies.

Examples

Uses a timeout classifier, an HTTP request, a resumable file download, and a five-minute HTTP client timeout.

What it assumes

Assumes HTTP connections and Go error handling while distinguishing timeout behavior across standard networking packages.

What you can do after

Builds Go HTTP operations that detect timeout errors, resume downloads, retry bounded failures, and report unrecoverable errors.

How it connects

Connects timeouts with retries, HTTP connections, error handling, logging, and alert systems.

liveBookmanning.com

Read Go in Practice, Second Edition on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Elixir in Action, Third EditionFault tolerance is the ability of a system to continue providing acceptable service when components fail or errors occur.
• 

  liveBookmanning.com
  Amazon Web Services in Action, Third Edition: An in-depth guide to AWSA fault-tolerant service continues providing its intended functionality despite failures in components or infrastructure.
• 

  liveBookmanning.com
  Quarkus in ActionFault tolerance is the ability of a system to continue providing acceptable service despite failures in its components or dependencies.
• 

  liveBookmanning.com
  Effective Platform EngineeringResilience is the ability of a system to continue providing acceptable service or recover when experiencing faults, disruption, or degraded conditions.
• 

  liveBookmanning.com
  Platform Engineering on KubernetesResilience is the ability of an application or service to continue providing useful functionality despite failures in its components or dependencies.
• 

  liveBookmanning.com
  The Art of CodeResilience is the ability of a software system to continue providing acceptable behavior during disruptions and recover from failures.
• 

  liveBookmanning.com
  Architecting an Apache Iceberg LakehouseFault tolerance is the ability of a system to continue operating correctly or recover without unacceptable data loss or corruption after component failures.
• 

  liveBookmanning.com
  Data-Driven CybersecurityAn organization’s ability to prepare for, withstand, adapt to, and recover from disruptive events such as cyberattacks.
• 

  liveBookmanning.com
  Kafka for ArchitectsFault tolerance is the ability of a system to continue providing its required behavior despite failures in components or dependencies.
• 

  liveBookmanning.com
  LatencyFault tolerance is the ability of a system to continue providing acceptable service despite failures of components or dependencies.
• 

  liveBookmanning.com
  Lead Developer Career GuideThe ability to remain effective and recover while facing difficulty, pressure, or setbacks.
• 

  liveBookmanning.com
  Think Distributed SystemsThe ability of a system or protocol to continue providing acceptable behavior despite component or network failures.

Compare how 13 books explain resilience →

Related concepts

• uptimecontrasts with · Uptime is the duration or proportion of a specified period during which a system or service is operational and available to provide its intended function.
• replicationaddressed by · Replication is the creation or maintenance of multiple copies of data, state, or functionality across separate locations or components.
• retryuses · A retry is a subsequent attempt to perform an operation after an earlier attempt fails or does not complete successfully.
• redundancycontrasts with · Redundancy is the presence of duplicate or overlapping information, components, or resources, whether intentional or unnecessary.
• Tree-of-thoughtproduced by · Tree-of-thought is a reasoning technique that explores and evaluates multiple branching paths of intermediate reasoning to develop a solution.

This explainer was generated by Manning's knowledge graph from the text of Go in Practice, Second Edition. The section links point to the parts of the book it draws on.