Count one hit against the named limiter.
What the budget belongs to.
How many hits the window allows.
How long the window lasts.
Optionalname: string
Which limiter counts it.
The verdict.
The limiter a rule named, or the default.
The limiter's name.
The limiter.
Register a built limiter.
The name rules refer to it by.
The limiter.
This manager.
Register a limiter to be built on first use.
The name rules refer to it by.
How to build it.
This manager.
StaticcreateThe limiter used when a rule names none.
A manager.
StaticgetThe published manager, if there is one.
StaticsetPublish the manager, so code outside the container can reach it.
Optionalmanager: RateLimitManager
Holds the configured limiters and hands one out by name.
The same shape every driver-based module in the framework uses: named limiters, a default, and factories so an application can register a driver this package has never heard of. That last part matters more here than elsewhere: a limiter has to live where the application's other state lives, and for a serverless deployment that is often the table it already runs on.