Backpressure: Why “Just Handle More Traffic” Is the Wrong Mindset

When we talk about scaling systems, the default thought is: “How do we handle more requests?” But the better question is: “What happens when we receive more than we can handle?” That’s where backpressure becomes important. Not as a buzzword. As a stability mechanism. The Real Problem In any backend system, different components have different capacities. API receives 10k requests/sec Service layer handles 6k/sec Database handles 3k/sec That gap doesn’t disappear — it accumulates. It turns into: Growing queues Thread pool exhaustion Memory pressure High GC Increased latency Eventually → failure. Backpressure exists to prevent that. So What Is Backpressure? At its core: Backpressure is a flow-control mechanism in which the consumer controls how much data it receives from the producer. Instead of: Producer → pushes endlessly Consumer → keeps accepting We get: Consumer → “Give me 100. I’ll ask again when ready.” That simple shift changes system behaviour completely. This Is Not Just a React