I'm on a shared hosting instance with relatively low resource allocation but reasonable bandwidth, and made #1 several times while never having issues loading. As long as your content is static and doesn't generate load on your server, you should be fine serving a lot of concurrent requests. Issues start when serving content relies on a database, or you serve large content
I mean not really, as always you just need to make sure you're not doing 10s of dynamic calls for each page load and if you do, add some minute-long cache at least. Most of the stuff that gets hugged to death really shouldn't, most of the times it's just static content that is trivial to host on even $10/month instances.
The amount of calls on some pages displaying the simplest stuff is mind-boggling. 160 requests for a page just displaying a HTML5 video and a title, 360 requests for a Reddit page, it's nuts. We don't need to be like this.
"We and our 350 partners care about your privacy".
Iirc HN itself does not have a CDN.
It was not my intention to bring the HN hug of death.
(For a reference, I shared a link, I am not the author.)
caching is the solution. don't serve dynamic content w/o html caching.
LLM vibe coded site and architecture?
Dumping things on Cloudflare is clever architecture now?
How many microservices, sql joins, distributed kafka piplelines etc. we currently recommend for serving static, public article?