Throughput

The amount of work a system can complete over time, such as requests, events, records, or bytes per second.

Why it matters

Throughput is useful because it gives engineers a shared vocabulary for designing, building, reviewing, and operating real systems. It helps teams reason about tradeoffs, failure modes, performance, and maintainability instead of treating implementation details as isolated facts.

Where it fits

This concept belongs in the software track, inside the system-design layer. It often appears alongside latency, bottleneck.

Mental model

Think of Throughput as a named pattern or capability. When you can recognize it, you can ask better questions: what problem does it solve, what assumptions does it make, what can fail, and what neighboring concepts should be considered?

Common mistakes

• Treating the term as a buzzword instead of connecting it to concrete engineering decisions.
• Ignoring related constraints such as scale, security, ownership, observability, and failure recovery.

Related concepts

Study this together with latency, bottleneck to understand how it behaves in a larger system.