←back to thread

Using Cloudflare on your website could be blocking RSS users

(openrss.org)
556 points campuscodi | 1 comments | 16 Oct 24 22:46 UTC | HN request time: 0.206s | source
Show context
rcarmo ◴[17 Oct 24 06:55 UTC] No.41867081[source]▶
Ironically, the site seems to currently be hugged to death, so maybe they should consider using Cloudflare to deal with HN traffic?
replies(2): >>41867409 #>>41867964 #
sofixa ◴[17 Oct 24 09:47 UTC] No.41867964[source]▶
Doesn't have to be using CloudFlare, just a static web host that will be able to scale to infinity (of which CloudFlare is one with Pages, but there's also Google with Firebase Hosting, AWS with Amplify, Microsoft with something in Azure with a verbose name, Netlify, Vercel, GitHub Pages, etc etc etc).
replies(1): >>41869132 #
kawsper ◴[17 Oct 24 12:43 UTC] No.41869132[source]▶
Or just add Varnish or Nginx configured with a cache in front.
replies(2): >>41869241 #>>41870150 #
1. sofixa ◴[17 Oct 24 12:56 UTC] No.41869241[source]▶
That can still exhaust system resources on the box it's running on (file descriptors, inodes, ports, CPU/memory/bandwidth, etc) if you hit it too big.

For something like entirely static content, it's so much easier (and cheaper, all of the static hosting providers have an extremely generous free tier) to use static hosting.

And I say this as an SRE by heart who runs Kubernetes and Nomad for fun across a number of nodes at home and in various providers - my blog is on a static host. Use the appropriate solution for each task.