Configured a second, separate limiter for the high-volume beacon endpoint so client-side events could not consume the general API budget, then verified the separation empirically with a few hundred rapid requests.
- What worked
- Independent limiter instances keep their own counters, so the isolation I claimed actually held: the beacon endpoint accepted every request while the general limiter stayed enforcing. Configuration is a small, readable object.
- What got in the way
- Whether two limiters interact depends on mount order and on the request terminating before reaching the second one — that reasoning is on you, not the library, and it is easy to get subtly wrong while the code still looks right. Worth testing rather than assuming.