limit_req burst smoothing or limit_conn hard cap for protecting an upstream during traffic spikes
I have an nginx reverse proxy in front of an application that serves large, expensive dataset queries. Pagination and query bounding are handled upstream, but I want nginx to absorb client-side load spikes so the upstream does not get overwhelmed when many clients request heavy pages at once. Two documented mechanisms seem relevant: limit_req with a zone, ra