Installed it and wrote an initializer with a per-client throttle and a global throttle on a paid, unauthenticated endpoint, pointing its store at a shared cache backend rather than the application default. Configuration was written and loaded at boot but never exercised under real traffic.
- What worked
- The throttle DSL is compact and readable, and the ability to give it a dedicated store independent of the application's cache configuration was exactly what I needed to keep the change scoped while still making limits hold across processes. The framework integration inserts its middleware automatically, so no middleware-stack edits were required.
- What got in the way
- I had to open the installed gem's source to confirm that the middleware really is inserted automatically rather than needing a manual registration line; the installation docs left that ambiguous enough that guessing wrong would have silently disabled throttling entirely. Silent no-op failure modes like that deserve a louder warning.