Apigee Spike Arrest: How the Bucket Actually Works

A visual guide to 429s, rate normalization, and the token bucket behind Apigee SpikeArrest.

Apigee SpikeArrest is easy to describe as a request limit, but that shorthand hides the detail that matters when traffic arrives in bursts. A policy can allow the same average throughput while producing very different results depending on whether its rate is expressed per second, per minute, or per hour.

This interactive deck walks through what a 429 Too Many Requests response means, how clients should retry with backoff and jitter, and how Apigee derives burst capacity from the configured rate. The central idea is simple: there is no separate MaxBurst setting to tune. The bucket is shaped by the rate and its unit, so understanding those units is the key to predicting the behavior.