Really need to use a CDN before you get #1 on HN

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.

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?

not if you have a static site