Request-Pattern Aware Backpressure Control

[abbasbaman]

Right now, Ingress and Gateway APIs route traffic based on host, path, headers, etc. However, they don’t offer any traffic-shaping or backpressure control based on dynamic request content particularly in cases where backend services may accept only certain patterns or can degrade with specific large payloads or special API calls.

GraphQL APIs with large @include fields can overwhelm downstream services.

Certain REST endpoints (e.g., reporting endpoints, file upload endpoints) cause spikes in memory/CPU due to payload size or processing complexity.

Under high traffic, you might want to throttle or reject specific patterns like large query parameters, multi-part uploads, or heavy search filters—not just by rate limiting, but based on content complexity.