Course contentsShow
← System Design
Lesson 959 of 1,91925. Rate Limiting and ThrottlingFree lesson

Hard vs Soft Limits

Compare rejecting requests immediately versus allowing bursts with eventual enforcement of limits.

Hard vs Soft Limits

What you'll learn: How rate limiting strategies differ between immediately rejecting excess requests (hard limits) versus allowing temporary bursts before enforcement (soft limits).


When implementing rate limiting, you face a critical design choice: should you strictly reject every request that exceeds your defined threshold, or should you allow some flexibility?

Hard Limits: The Strict Bouncer

A hard limit immediately rejects any request that would exceed your rate limit. If a client is allowed 100 requests per minute and tries to make the 101st request, it receives an instant rejection (typically HTTP 429).

Think of it like a nightclub with a strict capacity limit: once you hit 100 people inside, the bouncer turns everyone else away immediately, no exceptions.

When to use:

  • Protecting critical resources from overload
  • Preventing abuse or DDoS attacks
  • Enforcing contractual SLA limits
  • Databases or services with hard capacity constraints

Soft Limits: The Flexible Approach

A soft limit allows brief bursts above the limit, typically using techniques like token buckets that can accumulate unused capacity. A client might exceed 100 req/min momentarily if they've been under-utilizing their quota, but sustained violations eventually trigger enforcement.

This is like a bouncer who might let 105 people in during a brief rush, knowing that 10 people are about to leave.

When to use:

  • Improving user experience for bursty traffic patterns
  • Gradual degradation instead of hard failures
  • Warning users before full enforcement
  • Systems that can tolerate brief overages

The Middle Ground

Many systems combine both: soft limits with warnings (HTTP 429 with Retry-After header but request still processed) escalating to hard limits for persistent violators.

Key Takeaway: Hard limits provide strict protection but poor user experience during bursts; soft limits offer flexibility and better UX but require more complex implementation and monitoring to prevent sustained abuse.