Multi-instance Rate Limiting

By default, the web reverse proxy uses a local instance specific in-memory cache to track and store rate limiting data.

The web reverse proxy can be configured to track and store rate limiting data in a Redis database. When rate limiting data is stored in a Redis database, multiple instances can share this same data and rate limit clients across multiple instances.

This capability uses the [redis-collection:<name>] stanza to define details about the Redis server(s) which will be used to store data. See Defining Redis servers [redis-collection:<collection-name>] stanza.