3 ms·
Another advantage is you can put your _entire_ website on a CDN provider like Cloudflare, because the whole site is static. This means my server can die complet
by giobox 9y ago
Another advantage is you can put your _entire_ website on a CDN provider like Cloudflare, because the whole site is static. This means my server can die completely, but Cloudflare can still keep on serving my site, and my readers have no idea of my ineptitude.
You can do this even with Cloudflare's free tier - no need to rely primarily on adding more VPS instances/load-balancing to 'scale' your static site - the CDN can help take care of this. I've recently moved my Jekyll based blog to the cheapest VPS instance I could find, and use CloudFlare to handle the load (not that it has much in the way of readers...).
- rgbrenner 9y agobe careful relying on that though.. Each pop has it's own cache, and when there's a miss, it'll hit your server. Its pretty rare that a CDN gives you any insight into their caches, and there's no guarantee a file is kept in the cache. A file can be removed from the cache for many reasons--cache filled; file not popular enough; etc. So even if your local pop is saying the file is cached.. the other pops may not have any files for your website at all... or might be missing parts of the page (images, etc). (The x-cache header only indicates the status of the file at the pop that served the request -- not all pops.)