error-handling-patterns

Standardize error handling in a Node.js TypeScript backend by implementing a unified AppError hierarchy, mapping domain errors to HTTP statuses, and wiring middleware for consistent API responses. This replaces ad-hoc errors across services.

A no-throw Result type for safer error propagation is a pattern that returns success or error values instead of throwing exceptions. This prevents unhandled rejections and makes call outcomes explicit in TypeScript backend code.

Avoid unhandled promise rejections in Express async routes by wrapping route handlers with an async handler wrapper. This catches rejected promises and forwards them to centralized error handling middleware for safe logging and mapping.

The best way to implement retry patterns for flaky external API calls is to apply dedicated retry utilities that re-attempt failed requests. This builds resilience into microservice backends dealing with unreliable external dependencies.

Yes, you can use this error handling middleware for microservice backends. The approach applies to API services and microservices requiring robust error handling, consistent API responses, and safe error exposure across distributed systems.

Map domain errors to HTTP status codes in TypeScript by defining an AppError hierarchy with built-in status mappings. Centralized middleware intercepts these errors to produce consistent API responses and ensure safe error exposure to clients.