For reference: with cached HTML, my single Node.js process running on Heroku's cheapest tier has weathered the front page multiple times without breaking a sweat
OP may or may not feel the same! Just wanted to communicate that a simple server can definitely do the job
Makes sense for a lot of things, but it comes with downsides, especially for hobbyists! I've found I prefer sticking with a simple server for my website, and OP might find it's easier to do that too
It's just a cache that returns content faster than the original content.
> A content delivery network, or content distribution network, is a geographically distributed network of proxy servers and their data centers. The goal is to provide high availability and performance by distributing the service spatially relative to end users.
Emphasis mine. CDN implies some sort of edge-hosting topology (or at least more-proximal than the main servers).
>CDNs act as trusted overlay networks that offer high-performance delivery of common Web objects, static data, and rich multimedia content by distributing content load among servers that are close to the clients.
and:
>CDNs first emerged in 1998 to address the fact that the Web was not designed to handle large content transmissions over long distances.
[0]: https://ieeexplore.ieee.org/document/1250586
[1]: https://link.springer.com/book/10.1007/978-3-540-77887-5
I think the criteria are that it a) delivers/distributes content b) is a network, implying multiple nodes c) lowers the latency and/or bandwidth cost of data consumption, by d) leveraging geographically distributed redundancy and/or proximity. I think the key feature is geographically distributed redundancy which differentiates it from a regular cache.
But as my blog is entirely static (except for the comment threads, hosted on my Discourse forum), I just let CloudFlare serve it. I had to do some tweaks to the configs to say, "No, really, cache everything!" (it doesn't do that by default for a range of very valid reasons, none of which apply to me), but once that change went in, I'll see 98.5% or higher "served out of cache" ratios when I'm seeing a lot of traffic from HN or somewhere.
I'd originally designed it to be hosted out of a Google Cloud bucket with CloudFlare (egress traffic is cheaper that way than out to the internet), but I eventually decided to host on my server, as I could then do Tor and some other stuff more easily. I've got the server anyway...
One of these days, I may play with dropping analytics entirely and just passing requests through to my server, let images remain cached as that's the bulk of my bandwidth. Then I can go even more oldskool and parse my server logs for stats and referrers and such!
Expect to see a bunch of bots. I tried setting up server-side analytics for a WordPress-based website, but I had to get rid of it as the bot traffic made it essentially useless.
If your website is a collection of static files and you're hosting them on S3+CloudFront or something similar (GitHub pages works too), then it'll work without any issues and cost pennies for the whole thing.
1,000,000 uniques over 3 days in ~2011.
I have been trying to re-create that high ever since, lol. Going viral is one hell of a drug.
Total traffic both times was around 60k over the course of 2-3 days.
https://nginx.org/en/security_advisories.html shows one "medium severity" vulnerability in the last 4 years.