Building a High Performance, Dynamic CDN with Next.js
summary
A Next.js banner system that serves personalized HTML and CSS reaches 12,000 requests per second after swapping React for Inferno, moving server rendering data fetching into a Go service, and placing nginx caches with short TTLs in front of the origin a one‑page load drops to ~100–200 ms by removing unnecessary JS and shipping only critical HTML and CSS the team aims for a 200 millisecond goal and pairs Cloudflare edge routing with regional hosting and strict ephemeral data deletion
AI-written summary · about
chapters (17)
- 0:00Building dynamic CDN with Next.js
- 1:31Speed matters for engagement
- 2:35User request flow design
- 2:57Measuring Next.js with wrk
- 4:21Optimizing React bundle size
- 5:25Testing Preact and Inferno
- 6:31Reducing JS for load times
- 7:57API requests impact
- 8:59Data fetching in Go service
- 9:41When to use nginx
- 10:24Caching dynamic content
- 11:06Second nginx layer
- 12:10Commercial CDN distribution
- 13:36Static bundles for changes
- 14:41Minimizing network requests
- 15:22Dynamic data handling principles
- 16:03Scaling across cloud regions
