What is Backpressure in Distributed Systems?

Backpressure in distributed systems is a flow-control mechanism to prevent overload by signaling producers to slow down when consumers cannot process data quickly enough.

When to Use

Use backpressure in streaming pipelines (like Kafka), real-time APIs, or microservices handling sudden traffic spikes.

Example

In a one-barista coffee shop, if too many orders arrive at once, the barista slows new intake until they catch up—this is backpressure in action.

Want to master these concepts for interviews?

Explore Grokking System Design Fundamentals, Grokking the System Design Interview, or practice with Mock Interviews with ex-FAANG engineers.

Why Is It Important

Without backpressure, overloaded services risk crashes, memory leaks, or cascading failures. It ensures stability, resilience, and fairness in distributed systems.

Interview Tips

Explain it clearly with an analogy. Mention techniques like throttling, bounded queues, or pull-based models. Showing practical understanding scores high in interviews.

Trade-offs

You trade peak performance for reliability. While throughput may drop, the system avoids meltdown under heavy load.

Pitfalls

A common mistake is relying on infinite queues, which delay failure rather than prevent it. Another is ignoring monitoring, making backpressure invisible until too late.