Spring Cloud · Rate Limits

Spring Cloud Rate Limits

Spring Cloud is a set of self-hosted libraries (Config Server, Gateway, Eureka, etc.) — there is no vendor-hosted API and therefore no vendor-imposed throughput limits. Operators define their own throttling using Spring Cloud Gateway's RequestRateLimiter filter (Redis-backed token bucket) or Resilience4j RateLimiter. Numeric limits are entirely operator-determined.

Spring Cloud Rate Limits is the machine-readable rate-limit profile for Spring Cloud on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 1 rate-limit definition, measuring varies.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Circuit Breaker, Cloud Native, Distributed Systems, Java, and Microservices.

1 Limits Throttle: 429
Circuit BreakerCloud NativeDistributed SystemsJavaMicroservicesService DiscoverySpring FrameworkRate Limiting

Limits

Operator-Defined (Spring Cloud Gateway / Resilience4j) deployment
varies
see operator gateway and Resilience4j configuration
Effective limits depend on the RequestRateLimiter filter (replenishRate, burstCapacity) or Resilience4j RateLimiter configuration the operator deploys.

Policies

Self-Hosted Throttling
Spring Cloud Gateway emits a 429 with Retry-After when the configured token bucket is empty. Resilience4j RateLimiter throws a RequestNotPermitted exception that the application maps to 429. Both are configured per-route by the operator.
Distributed Coordination
Multi-instance deployments require a shared store (Redis is the documented default for Spring Cloud Gateway's RequestRateLimiter) so the bucket is consistent across replicas.

Sources