liveBook · Manning

Error handling

Error handling is the practice of detecting, representing, propagating, reporting, and responding to errors or failures during software operation.

How 5 Manning books explain it

Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform

An error-handling strategy is a systematic approach for detecting, responding to, and recovering from software errors.

How it is used
Plans responses and recovery to minimize harm when application errors occur.
How deep it goes
Explains anticipated-error responses and names two unexpected-error strategies, but does not detail the resume approach.
Examples
Uses runtime exceptions, faulty input, unexpected code use, failing dependencies, and Node.js uncaught-exception handlers.
What you can do after
Apply a strategy by planning retries, corrections, notifications, or process abort-and-restart responses.

Read how Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform explains error handling →

Effective Conversational AI

Error handling is the management of recognition, interpretation, or execution failures so that a system can recover or guide the user toward an appropriate outcome.

How it is used
Guides voice bots through recognition misunderstandings and highlights how missing-information dialogue can frustrate users.
How deep it goes
Explains clarification and response simplification, then illustrates an LLM repeatedly questioning users who lack required details.
Examples
Uses speech misunderstandings and a claim-status chat where the user lacks a member ID or other required details.
What you can do after
Evaluate generative dialogue flows for missing-information loops and identify clarification or repetition as voice-bot recovery options.

Read how Effective Conversational AI explains error handling →

gRPC Microservices in Go

Error handling is the practice of detecting, representing, and responding to failures during software execution or communication.

How it is used
Guides client decisions when gRPC communication between microservices fails.
How deep it goes
Works through status codes and Go validation-detail parsing, without descending into gRPC protocol internals.
Examples
Uses an Order service Create request with invalid fields and a ResourceExhausted order-limit response.
What you can do after
Apply it via Go gRPC status conversion to inspect validation errors and choose a response to service failures.

Read how gRPC Microservices in Go explains error handling →

Secrets of the JavaScript Ninja, Second Edition

The practice of detecting and responding to errors that occur during program execution.

How it is used
Frames error handling as a callback weakness and a reason to use promise chains for asynchronous sequences.
How deep it goes
Compares try-catch limits around callbacks with Node-style error arguments and catch handling across a promise chain.
Examples
Uses nested ninja-data callbacks and a chained sequence of mission requests.
What you can do after
Understand why asynchronous callback timing can bypass surrounding try-catch and how chained catch handles earlier promise failures.

Read how Secrets of the JavaScript Ninja, Second Edition explains error handling →

Starting Data Analytics with Generative AI and Python

A technique for detecting, responding to, and recovering from software or service failures.

How it is used
Stabilizes generative AI integrations when requests encounter errors or timeouts.
How deep it goes
Recommends retries for timeouts and rate limits but gives no implementation steps.
Examples
Names timeouts and rate-limit errors as cases for retry handling.
What you can do after
Apply retry mechanisms to handle request timeouts and rate-limit errors.

Read how Starting Data Analytics with Generative AI and Python explains error handling →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.