Anything the driver needs.
OptionaldriverWhich driver builds it. Defaults to memory, and ignored when factory is given.
OptionalfactoryBuild the limiter yourself, instead of naming a driver this package ships.
This is how a deployment counts in the store it already runs on. It is declared here, next to the other limiters, rather than registered on the manager from a provider: the container is rebuilt for every event, so anything registered imperatively during one event is gone for the next, and an application should not have to know that to plug in a driver.
The name it is resolved under.
What a configured limiter declares.