Throughput measures the requests or data volume a system processes per second. It describes how much work the system handles, unlike load, which describes the amount and kind of work demanded, or scalability, which describes handling increases in load. section 2.2.4
Use throughput as one part of a load profile:
- Compare peak scenarios, not just average demand; traffic can arrive in daily, seasonal, or campaign-driven waves. section 2.2.4
- Assess components separately: read-heavy paths, write-heavy paths, user interactions, and background processing can have different throughput needs. section 2.2.4
- Compare service tiers before discussing solutions; similar features can sit at very different throughput and cost levels. section 2.2.6
Table 2.4 Load tiers
|
Tier
|
Peak concurrency
|
Throughput
|
Architecture implications
|
|
Consumer storefront
|
50,000–100,000 concurrent users
|
5,000–15,000 req/s
|
Autoscaling, CDN, read replicas.
|
|
B2B
|
1500–2,000 concurrent users
|
100–500 req/s
|
Fixed capacity, vertical scaling sufficient
|
|
Internal backoffice
|
50–200 concurrent users
|
10–50 req/s
|
Single cluster, no autoscaling needed
|
|
Background processing
|
Low concurrency
|
High data volume, latency-tolerant
|
Batch jobs or stream processing, queue-based workers
|
Compare example throughput and concurrency tiers for storefront, B2B, backoffice, and background processing systems. section 2.2.4































