liveBook · Manning

Throughput

As explained in Automating API Delivery

Throughput is the amount of work or number of requests processed by a system within a specified time interval.

Throughput, or request rate, measures how many requests an API processes within a time window. In the RED method, it is one of three service metrics, alongside error rate and duration. section 11.2.1 section 11.2

Tracking request rate across different periods helps reveal API usage trends and patterns. API teams use it as part of technical performance monitoring; product metrics also inform decisions and improvement goals. section 11.2.1 section 11.4

Choosing a time window

Measure requests per second or minute for short-term activity, or compare request volumes per week or month to examine longer-term usage. section 11.2.1

How Automating API Delivery covers it

How deep it goes
Defines requests processed per time window and relates measurement periods to usage trends.
Examples
Uses per-second, per-minute, per-week, and per-month request measurements.
What you can do after
Evaluate API usage trends by measuring requests across selected time windows.
How it connects
Pairs request rate with error rate and duration in the RED method.

Also explained in

Compare how 20 books explain throughput →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Automating API Delivery. The section links point to the parts of the book it draws on.