Expand description
Pluggable counter backends for rate-limiting plugins.
The featherbit analogue of APISIX’s policy: local | redis counter
abstraction. Rate-limit plugins (limit-count, api-breaker, …) resolve a
per-client key, then ask a CounterStore to count it within a fixed
window. local (in-memory, per gateway instance) is always available; a
Redis-backed store for cross-instance limits is planned behind a feature
flag and slots in as another CounterStore implementation.
Structs§
- Counter
Error - Counter backend failure (e.g. an unreachable Redis). Plugins decide
whether to fail open (
allow_degradation) or reject. - Counter
Store Registry - Resolves a
policyconfig value to a counter backend. - Local
Counter Store - In-memory fixed-window counters (per gateway instance).
- Window
Result - Outcome of counting one request against a fixed window.
Traits§
- Counter
Store - A backend that counts requests per key within fixed time windows.