PricingPricingDocsDocsBlogBlogBook a demoBook a demoCompanyCompany (opens in a new tab)
Product
DocsAPI ReferencePricingConsole DemoBlogCompany
Start Freev3.4.7
Wave Flow

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.

The challenge

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.

Requests fail, then only low-priority requests are rejectedWithout WaveWith Waverequests faillow priority shed
Without Wave
A spike reaches the service and requests fail, checkout includedCRITICALcheckoutIMPORTANTloginMODERATEsearchBULKrecommendationsserviceoverloaded5xx5xx5xx5xx
When load passes capacity, checkout can fail with 5xx errors along with everything else.
With Wave
Low-priority requests are rejected first, checkout still worksCRITICALcheckoutIMPORTANTloginMODERATEsearchBULKrecommendations503503WaveFlowservicehealthyrejected at once
Wave Flow sorts requests into four priority tiers at the gateway. Under load it rejects the lower tiers with HTTP 503, so critical requests keep working.

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

From a traffic spike to a rejected request
Istio by defaultCheckout rejected like any request
  1. Ingress Gateway
    forwards every request; limits default to 2^32-1
  2. ↓you add→
    EnvoyFilter
    local rate limit: a token bucket counts requests per minute
  3. ↓429 when over→
    DestinationRule
    circuit breaker: caps connections and pending requests per host
  4. ↓503 when over→
    Service
    checkout is rejected the same as recommendations
Wave FlowCheckout keeps working
  1. Traffic Rules
    four tiers, matched by header, path, and method
  2. ↓policy→
    Wave Agent
    deploys the WASM module to the proxy
  3. ↓WASM filter→
    Ingress Gateway
    the filter sorts each request before routing
  4. ↓under load→
    Shed decision
    BULK first, CRITICAL never, HTTP 503 immediately
Istio: rate limit and circuit breaking tasks, DestinationRule reference, istio.io. Wave: Wave Flow docs. Request types are illustrative.
1

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.

2

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.

3

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.

Related in Wave Flow

NetFUNNEL Integration →Read the docs →
Book a demoStart free
Product
Wave GPUAI Infrastructure Professional ServiceWaveWave AI Agent2026 Q4
Resources
DocsAPI ReferenceBlogConsole DemoPricing
Company
STCLabBook a demoContact
STCLab© 2026 Wave All rights reserved.
Terms of ServicePrivacy PolicyCookies