The most common timeout value I see in production codebases is 30 seconds. It's almost never the right choice. Here's why most timeout configs silently make outages worse, and what to set instead.
- Published On
distributed systems
- Every 30 minutes, the auth server spiked to 100% CPU and shed requests. The pattern was so regular you could set a watch by it. Turned out every user's JWT expired at the same time.
- Published On
- A consulting story about a nightly billing job that quietly started double-charging customers after a Kubernetes migration — and the boring lock that finally fixed it.
- Published On
Tags
consulting (91)architecture (40)debugging (39)developer-experience (28)reliability (22)devops (15)ai (13)code-quality (11)performance (11)databases (9)observability (9)security (7)microservices (6)postgres (6)engineering-culture (6)technical-debt (6)database (6)kubernetes (5)postgresql (4)api-design (4)ci-cd (4)infrastructure (4)testing (4)productivity (4)distributed-systems (3)nodejs (3)dependencies (3)javascript (3)tooling (3)typescript (2)migration (2)on-call (2)refactoring (2)configuration (2)resilience (2)cost-optimization (2)code-review (2)deployment (2)opentelemetry (2)monitoring (2)goals (2)disaster-recovery (1)developer-tooling (1)build-systems (1)elasticsearch (1)github-actions (1)data-integrity (1)retention (1)authentication (1)node.js (1)data (1)websockets (1)project-management (1)mcp (1)finops (1)multi-tenant (1)authorization (1)terraform (1)dns (1)opinion (1)memory (1)error-handling (1)secrets-management (1)webhooks (1)containers (1)environments (1)queues (1)cloud (1)orm (1)alerting (1)incident-management (1)caching (1)platform-engineering (1)feature-flags (1)api (1)contracts (1)logging (1)mongodb (1)workflow (1)nestjs (1)angular (1)sandbox (1)sonarcube (1)learning (1)journey (1)mdx (1)