Where do you enforce limits: at the edge (gateway/CDN) or in the app? Explain the split.

Problem Statement

Explanation

Put coarse, cheap checks at the edge to drop obvious abuse close to the user and save bandwidth. Enforce authenticated, precise quotas in the app or gateway where identity is known. Use shared keys and bloom filters to communicate hot offenders to edges quickly. Keep the source of truth in one control plane to prevent drift. Propagate policy and counters via quick, eventually consistent channels with periodic reconciliation.

Code Solution

SolutionRead Only

Edge: IP burst shield; App: per-key token bucket + daily quota

Practice Sets

This question appears in the following practice sets:

Rate Limiting & Traffic Shaping

Next Question

Master Interviews
Anywhere, Anytime

Where do you enforce limits: at the edge (gateway/CDN) or in the app? Explain the split.

Problem Statement

Explanation

Code Solution

Practice Sets

Related Questions

Which statement best describes the Single Responsibility Principle?

Open–Closed Principle encourages what practice when adding features?

High-Level Design (HLD) typically focuses on which artifacts?

Which UML diagram best captures interactions over time between components?

Which pairing describes a healthy design goal?

More from System Design

Master Interviews Anywhere, Anytime

Where do you enforce limits: at the edge (gateway/CDN) or in the app? Explain the split.

Problem Statement

Explanation

Code Solution

Practice Sets

Related Questions

Which statement best describes the Single Responsibility Principle?

Open–Closed Principle encourages what practice when adding features?

High-Level Design (HLD) typically focuses on which artifacts?

Which UML diagram best captures interactions over time between components?

Which pairing describes a healthy design goal?

More from System Design

Master Interviews
Anywhere, Anytime