CDN Configuration Tools
Configuring content delivery networks to cache and serve assets close to users.
No CDN layer exists. Decentralized.Host's edge hosts are L7 proxies in front of replicas; there is no caching or points-of-presence network.
What a CDN actually does
A CDN puts copies of your static content (images, JS/CSS bundles, whole HTML pages for cacheable routes) on servers physically closer to each visitor, so a user in Singapore fetches from a nearby edge node instead of round-tripping to wherever your origin server actually sits. Configuration mostly means deciding what's cacheable (immutable assets like a hashed JS bundle: cache aggressively; a logged-in dashboard: don't) and for how long (Cache-Control/TTL headers), plus purge rules for when you deploy new content that must invalidate old cached copies immediately.
Configuring content delivery networks to cache and serve assets close to users. No CDN layer exists. Decentralized.Host's edge hosts are L7 proxies in front of replicas; there is no caching or points-of-presence network.