resource exhaustion
Running a service out of memory, time, connections or money by making it do unbounded work, whether by accident or on purpose.
One careless or hostile caller can take the service down for everyone.
In more detail
A single request for an unlimited page, an oversized body or a slow dependency without a timeout can be enough. Bound every list, body, queue and wait, and keep those limits in both the contract and the code.
Related terms
- pagination — Splitting a large collection into bounded pages, each with a way to ask for the next one.
- rate limiting — Capping how many requests a client may make in a period of time, and rejecting or delaying the rest.
- timeout — A limit on how long a caller waits for an answer before giving up.
- backpressure — A slow consumer signalling a fast producer to pause, so data does not pile up in memory faster than it can be handled.
Taught in
- Pagination Strategies — Modern API Architecture: REST, GraphQL & gRPC
- Security Best Practices — Modern API Architecture: REST, GraphQL & gRPC