Dead Letter Queue in Microservices: Handling Poison Messages
Learn how to design a dead letter queue in microservices: classify poison messages, bound message retry, enrich failures, and run safe DLQ replay with owners.
13 min read
Tag
error handling
gRPC Deadlines Error Handling: Status Codes and Propagation
Learn how gRPC deadlines propagate across services, how to choose and translate status codes, and how to retry safely without causing retry storms.
14 min read
Dead Letter Queue Guide: Handling Poison Messages Safely
Learn to classify poison messages, cap retries with backoff, capture failure context, and run safe, idempotent DLQ replay with owners and alerts.
16 min read
API Error Handling: Designing a Consistent, Versioned Error Contract
Treat API error handling as a public contract: HTTP status codes, stable error codes from a catalog, and RFC 9457 Problem Details bodies.
14 min read
Express.js in Production: Structure, Error Handling and Security
How to run Express.js in production: separate the app from the server, layer the code, centralize error handling and set a helmet-based security baseline.
14 min read
REST API Design: Resources, Status Codes and Consistency
Model resources as nouns, use HTTP methods and status codes per RFC 9110, and enforce conventions in CI so clients can predict every endpoint.
14 min read