NEW
Also known as: Request Timeout
A predefined limit after which an operation is aborted if no response or completion occurs.
DESCRIPTION
Timeouts bound resource usage and latency by canceling operations that exceed limits. They prevent indefinite waits, reduce cascading failures, and improve system resilience. Configurations exist at network, RPC, database, and application layers. Combined with retries and circuit breakers, timeouts form key reliability patterns. Proper tuning balances user experience, throughput, and fault isolation.
ALTERNATIVE DEFINITIONS
MDN Web Docs
The timeout property represents a time limit in milliseconds, after which the request will be terminated if it has not completed.
Focuses on client-side HTTP request timeout behavior.
gRPC
A deadline is a time by which an RPC should complete.
Defines RPC completion time constraint closely related to timeouts.
Kubernetes
timeoutSeconds: Number of seconds after which the probe times out.
Shows timeout configuration in container health probes.
RELATED TERMS
Circuit Breaker Backoff Deadline SLA Heartbeat Liveness Probe Connection Timeout Fail Fast Cancellation
COMPETING TERMS
KNOWLEDGE AREAS
Software Engineering Observability & Telemetry Data Engineering Infrastructure
TARGET AUDIENCE
DevOps Engineer Software Developer Cloud Architect IT Manager Security Architect
EXTERNAL SOURCES
- Wikipedia - Timeout (computing)
- MDN Web Docs - HTTP client timeout property
- gRPC - Deadlines and timeouts in RPC
- Kubernetes - Probe timeout configuration
TOP QUESTIONS
Why are Timeouts important in distributed systems?
They prevent indefinite waits, bound latency, and help isolate failures, improving overall resilience.
Category: Relevancy
How do Timeouts interact with Retries?
Retries resend failed operations. Combined with timeouts and backoff, they avoid overload and reduce tail latencies.
Category: Relationship
What mistakes occur when configuring Timeouts?
Overly long timeouts cause resource exhaustion; too short timeouts increase unnecessary retries and failures.
Category: Mistakes
How should Timeouts be tuned?
Base them on SLAs, observed latency, and criticality; apply jitter and exponential backoff to retries.
Category: Requirements
What risks arise from missing Timeouts?
Hangs, thread starvation, and cascading failures can occur, especially under partial outages.
Category: Risk
Are Timeouts different from Deadlines?
Deadlines set an absolute completion time; timeouts are duration-based limits. Both enforce constraints.
Category: Misunderstanding
How do Timeouts apply to databases?
Query and connection timeouts avoid long-running locks and contention, protecting throughput.
Category: Example
How to monitor Timeouts effectively?
Track error codes, retry counts, and latency distributions; alert on excessive timeouts and retry storms.
Category: Management
Where to learn more about Timeouts?
Review platform docs (MDN, gRPC, Kubernetes) and reliability patterns like circuit breakers and bulkheads.
Category: GettingStarted