Node.js Performance and Resilience

When to use

Invoke when a scaffolded Node.js service must hold an SLO under load: blocking work is starving the event loop, downstream failures cascade, there is no backpressure under burst, retries amplify outages, or there is no load-test gate proving the service meets its latency/throughput budget before release.

Do not use for: the service shell, config, or error tiers (use nodejs-service-scaffold), auth or OWASP review (use nodejs-auth-and-security-review), OpenTelemetry/metrics/SLO definition (use nodejs-observability-readiness), or broker/queue/event integration (use nodejs-queue-and-event-integration).

Inputs

Required:

• A service with the nodejs-service-scaffold baseline (config, logging, graceful shutdown, health probes present).
• Approved architecture/performance budgets and architecture/reliability SLO targets (latency/throughput objective, error budget) — or explicit confirmation they are intentionally deferred.

Optional: