Rules Hub
Code Ruleset
← Back to all rules
Rule priority, scope & exceptions
Use this to align rules with the senior-level structure (P0/P1/P2, scope, exceptions/tradeoffs).
backend ruleP2universalStack: node
timeoutshttpperformanceresilience
Keep network timeouts realistically short
Set network deadlines from the operation and caller latency budget; avoid arbitrary very long or universally short timeouts.
PR: hegnar-web · org-mining-hist-2026-06Created: Jun 19, 2026
Bad example
Old codetypescript
| 1 | fetch(url, { signal: AbortSignal.timeout(10_000) }); |
Explanation (EN)
An unbounded or unjustifiably long deadline retains work after it can no longer satisfy the caller.
Objašnjenje (HR)
Good example
New codetypescript
| 1 | fetch(url, { signal: AbortSignal.timeout(2_000) }); |
Explanation (EN)
Objašnjenje (HR)
Notes (EN)
Choose a deadline from the operation's latency budget, observed upstream behavior and retry budget; propagate caller cancellation.
Exceptions / Tradeoffs (EN)
Uploads, streaming, long polling and batch jobs need different deadlines. There is no universal two-second cutoff after which a response cannot arrive.