liveBook · Manning

Rate limit

As explained in Microservices Patterns, Second Edition

A rate limiter pattern restricts the frequency or volume of calls made to a resource or dependency.

A rate limiter caps how frequently a client calls a remote service, helping prevent overload. When the maximum rate is exceeded, the call attempt fails. section 8.2.4

In synchronous API composition, a provider proxy may use a rate limiter alongside other resiliency patterns. Choose it when controlling call frequency is needed; a bulkhead instead limits outstanding calls. section 12.3.3 section 8.2.4

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines the pattern and its failure when the maximum rate is exceeded, but gives no algorithm or configuration.
Examples
Places the pattern in synchronous remote calls and API-composition provider proxies, without a worked rate-limiting scenario.
What it assumes
Assumes familiarity with synchronous service calls and resiliency patterns; no prerequisites are taught from zero.
What you can do after
Apply it to limit how frequently a client calls a remote service.
How it connects
Relates rate limiting to API composition, provider proxies, bulkheads, retries, circuit breakers, and time limiters.

Also explained in

Compare how 19 books explain rate limit →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.