Course contentsShow
← System Design
Lesson 1087 of 1,91928. Timeouts and DeadlinesFree lesson

The Cost of Missing Timeouts

How missing timeouts leads to thread starvation, cascading failures, and degraded user experience across services.

The Cost of Missing Timeouts

What You'll Learn

You'll discover how failing to set timeouts causes thread exhaustion, cascading failures, and widespread system degradation.

The Problem: Waiting Forever

When a service doesn't define timeouts, requests to slow or unresponsive dependencies can hang indefinitely. Each hanging request consumes a thread or connection from a limited pool, waiting for a response that may never arrive.

Thread Starvation

Imagine a restaurant with 10 waiters. If customers never leave, new customers can't be served—even if the kitchen is ready. Similarly, without timeouts, threads get stuck waiting on slow backends. Eventually, all threads are occupied waiting, and your service can't handle new requests. Healthy requests that would normally succeed now fail because no threads are available.

Cascading Failure Amplification

The impact doesn't stop at one service. When Service A exhausts its threads calling Service B:

  • Service A becomes unresponsive
  • Services calling Service A now experience slowness
  • Their threads get stuck waiting on Service A
  • The failure cascades upstream through your entire system

What started as one slow database query or network hiccup becomes a company-wide outage.

Degraded User Experience

From a user's perspective, missing timeouts create the worst possible experience:

  • Requests hang for minutes before failing
  • Browser tabs freeze
  • Mobile apps become unresponsive
  • Users retry, creating additional load (retry storms)

With proper timeouts, users get fast failures they can understand. Without them, they're left in limbo, repeatedly clicking refresh and amplifying the problem.

Key Takeaway: Missing timeouts transform localized failures into resource exhaustion that cascades across services, turning small problems into complete outages—always set explicit timeout values on every network call.