Rate Limiting for the Paranoid
Token bucket, leaky bucket, and why most teams accidentally ship the wrong one for the traffic they have.
This is placeholder body copy. In a real post there would be an argument here, built one paragraph at a time, with the kind of small detours that make a technical essay feel like it was written by an actual human.
The repository this page lives in exists to demonstrate behavior of the Next.js router, so the content is intentionally boring. Any similarity to real insight is entirely coincidental, if occasionally welcome.
If you are reading this from a prefetch-triggered hover, congratulations, the link worked. If you are reading it after a full navigation, that also counts, and you have learned something about how caches behave under load.
More posts
Feature Flags That Do Not Leak
Keeping flag logic out of the UI and close to the boundary, so cleanup is a delete rather than an archaeology dig.
The Subtle Art of Cache Invalidation
A walk through tag-based, time-based, and event-driven invalidation, with their respective failure modes.
Typing Third-Party Libraries Without Tears
Ambient declarations, module augmentation, and other escape hatches for when DefinitelyTyped lets you down.