Adventures at HyperScale!
summary
Have I Been Pwned handles ~17 billion requests a month, serves ~430 TB, and stores ~6 billion unique emails plus ~1 billion password hashes while being run by two people. Architecture uses Cloudflare workers at the edge, Cloudflare CDN with Cloudflare cache reserve to avoid origin egress, and Azure for compute and storage with Azure SQL Hyperscale for main data; a custom autoscaler and prefix-sharded caches reduce origin load and the migration to SQL successfully cut backup and query bottlenecks.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:26Have I Been Pwned history
- 9:55Infrastructure and traffic scale
- 16:04Cloudflare caching limits issue
- 22:36Azure Tables to SQL Hyperscale
- 27:05SQL Hyperscale parallel queries
- 32:43SQL Hyperscale cost fixes
- 40:26Cloudflare Workers edge processing
- 44:44UI speed vs user experience
- 46:29System observability monitoring
- 51:00Key takeaways
related talks
37mHave I Been Pwned: Serving billions of requests and terabytes of data without going broke!
50mHave I Been Pwned?
56mWhat We’ve Learned From Billions of Security Reports
51mWhat We’ve Learned From Billions of Security Reports
31mStandard Classification: Live Q&A Session
01h 00mBuilding Safe Systems at Scale - Lessons from Six Months at Yahoo
01h 00mKeynote: How I Met Your Data
01h 00mHyper Speed: When Big Data Blooms
