Reading-path month: February 2026. Collection published on September 12, 2026. Months organize the reading path; they are not earlier publication dates.
Availability: budget expensive operations
Request counts can hide large differences in work.
Content produced with AI assistance for Thiago Silva’s website. Independent editorial analysis; it does not represent clients or employers.
Reading context
A short architecture article. The technical reference supports the topic; hypothetical scenarios and assessment proposals are editorial analysis, not accounts of personal implementations.
Original source ↗The architecture decision
Two calls to the same API can require very different effort. A simple query and a large export should not share a capacity assessment based only on request counts.
Practical application
Editorial proposal: classify operations by downstream work, including dependencies and queues. For a hypothetical report, constrain scope and concurrency using validated capacity. Plan the response when a caller exceeds its budget.
How to verify
During a controlled exercise, observe an expensive operation's degradation and impact on others. Ask whether the essential service remains usable. Record limits and recovery; blocking traffic while leaving a permanently congested queue does not resolve the problem.