Hi, We run a single DataPower Multi-Protocol Gateway (MPGW) with multiple processing rules. Occasionally, one client floods a specific request rule (10k calls), which are routed via ACE to our backend. The backend can’t sustain the surge (timeouts/thread pool exhaustion) and becomes unstable.We need a deterministic, inline mechanism at the gateway to prevent the surge from reaching the backend—ideally per partner and scoped to that rule/URI—without impacting other rules.
Question to the community: If you were in this situation, would you lead with SLM (policy-driven, no code) or GatewayScript (more custom control)Any field-tested configs, pitfalls, or references are much appreciated.
Tags: #DataPower #MPGW #SLM #GatewayScript #RateLimiting #DoS #SOAP #REST
Certainly lead with SLM because there is nothing you stated it cannot do. Then drive with GWS if the SLM doesn't cover it.
SLM, to be specific count monitor is a classic fit here.