SYSE.40:11 - SoTA-Echoing

For “How should a service behave when demand exceeds useful capacity?”, adapt the historical 2016 SRE Handling Overload resource-sensitive line. Reject QPS-only sizing and invisible refusal as adequate policy. Sections 4.1–4.4 connect resource cost, workload separation and the user’s actual outcome.

Compare the mechanism with current Envoy architecture and configuration documentation. Their monitor/trigger/action distinction makes local protection concrete, but latest/development examples neither qualify a deployed release nor protect every upstream. Reserved capacity and control maintenance are real trade-offs.

Reopen the envelope when request cost, workload mix, provider limits, failure behavior, retry layers or deployed protection mechanisms change. A successful earlier burst test does not qualify a new expensive task class.