- HTTP/3 on a CDN: what changes for real usersHTTP/3 runs on QUIC over UDP. It cuts handshake cost and some head-of-line blocking that TCP still shows on lossy links. The useful part: the browser talks HTTP/3 to the edge. Your origin can stay HTTP/1.1 or HTTP/2.
- How to self-host web fonts on a CDNFont files are small and on the critical path. A third-party font host adds DNS, TLS and privacy surface. Self-host WOFF2 on Cloud CDN under your hostname.
- How to put large file downloads on a CDNRelease day is a read storm. A single origin disk will saturate before 210+ caches would. Version the filename, cache for a long time, shield first-byte, and token-protect anything that should not be public.
- How to cache API GET requests at a CDNNot every API response needs a fresh origin hop. Public product, content and configuration GETs are often identical. Cache those. Never cache the ones that change with Authorization.
- Live streaming on a CDN: latency, shield and load testsA live audience is a miss storm with a clock. If every viewer opens the encoder, the show is the outage. Cache live segments at the edge with short TTLs, shield the packager, and rehearse.
- How to deliver video on demand through a CDNVOD is a cache problem dressed as a media problem. Segments and files are large, popular and identical. The encoder should package once. Cloud CDN should repeat the result on 200+ Tbps.
- WebP and AVIF at the edge: image optimization without a batch jobMost teams still generate derivatives at upload, then ship an overweight original to a phone anyway. Keep one source image. Let Cloud CDN convert, crop and resize at delivery time, then cache each variant at the edge.
- How to purge a CDN cache without melting originA cache you cannot invalidate is a liability. A purge that invalidates everything is an origin incident you scheduled. Purge the path that changed, prefetch what you know will be hot, and keep hashed assets out of the ritual.
- Origin Shield explained: stop miss storms from reaching originWhen a popular object expires, every edge can miss at once. Without a shield, the origin sees a fan-out of identical fetches — the thundering herd that looks like an attack but is only your own TTL.
- Django STATIC_URL and MEDIA_URL on a CDNIf STATIC_URL and MEDIA_URL still point at the same host that runs views, you are paying worker time for CSS. Point both at Cloud CDN and keep admin on Django.
- Laravel ASSET_URL and Mix/Vite on a CDNLaravel workers should run application code. They should not stream hashed Vite files and public disk images to every region. ASSET_URL and a media hostname exist so Cloud CDN can take that work.
- A Next.js CDN caching guide for App Router and ISRNext.js already thinks in cache. The mistake is leaving that cache in one region. Cloud CDN should hold /_next/static and shareable HTML at 210+ PoPs, with purge on deploy or revalidate.
- How to cache WooCommerce without breaking checkoutWooCommerce storefronts die on sale day because product images and category HTML share PHP workers with checkout. Cache the aisle. Never cache the cart.
- How to set up a CDN for WordPressWordPress spends PHP on the same CSS, uploads and anonymous HTML thousands of times per hour. Cloud CDN should take that traffic. wp-admin, login and checkout should not follow it into cache.