Wave Flow
Sorts requests at the Istio gateway into four priority tiers. Under load, it rejects the lower tiers with HTTP 503, so critical requests keep working.
A ticket sale opens, and traffic hits 4x the previous peak
Ticketmaster, statement on the Eras Tour presale, Nov 19, 2022; istio.io, DestinationRule reference and the rate limit and circuit breaking tasks.
Bot attacks and fans without codes drove 3.5 billion system requests to Ticketmaster, 4x its previous peak. Ticketmaster estimates that about 15% of interactions had issues, including passcode validation errors that made fans lose tickets in their cart.
By default, Istio sets no practical request limit: maxConnections, http1MaxPendingRequests, and http2MaxRequests all default to 2^32-1 (istio.io).
A rate limit or a circuit breaker you add counts requests or connections. It has no idea of priority: over the limit, a checkout request gets the same 429 or 503 as any other request on that route or host.
Request types are illustrative. Which tiers are rejected depends on load: IMPORTANT is rejected only under extreme load, CRITICAL never. Tiers and the 503 response are from the Wave Flow docs.
How Wave does it
- Ingress Gatewayforwards every request; limits default to 2^32-1
- you addEnvoyFilterlocal rate limit: a token bucket counts requests per minute
- 429 when overDestinationRulecircuit breaker: caps connections and pending requests per host
- 503 when overServicecheckout is rejected the same as recommendations
- Traffic Rulesfour tiers, matched by header, path, and method
- policyWave Agentdeploys the WASM module to the proxy
- WASM filterIngress Gatewaythe filter sorts each request before routing
- under loadShed decisionBULK first, CRITICAL never, HTTP 503 immediately
Sort requests into four tiers
In the Traffic Rules page of the Wave web console, or in a WaveFlowPolicy, you match requests to CRITICAL, IMPORTANT, MODERATE, or BULK by header, path, and method.
Run the filter in Istio
Wave Agent deploys Wave Flow as a WASM module to the Istio Ingress Gateway, a Sidecar, or an Ambient waypoint. The filter checks each request before routing.
Reject the lowest tiers first
Set a tier to Auto, and under load the filter returns HTTP 503 immediately: BULK first, then MODERATE, and IMPORTANT only under extreme load. CRITICAL is never rejected.