Closer to the Edge: Hyperscaling Have I Been Pwned with Cloudflare Workers and Caching

The post describes HIBP’s architecture shift to serving k-anonymity (six-character SHA‑1 hash prefix) search results from Cloudflare edge using Workers and cache reserve, turning a 16^6 request space into highly cacheable content that dramatically improves latency, availability, and cost efficiency. It explains how new breach loads force full cache flushes, the ensuing hit/miss recovery pattern, and the need to carefully manage origin capacity to avoid self‑induced DDoS-like spikes, while noting a persistent latency constraint from API key validation via Azure API Management and advocating for Cloudflare-native API management. The author provides traffic/cost observations, highlights benefits for Pwned Passwords (99%+ cache serve), and links to a livestream for deeper discussion.