3 ms·

Ironic that their "please don't share our links" post shared on HN also caused their website to crash. It's a 100% static blog post. Use a damn cache, or CDN, o

by paxys 3y ago

Ironic that their "please don't share our links" post shared on HN also caused their website to crash. It's a 100% static blog post. Use a damn cache, or CDN, or a hundred other ways of handling ~unlimited traffic for free. We are talking about a few thousand hits and tens of megabytes of total data transfer. It isn't 1998. This scale should not be a problem for anyone.

oefrha 3y ago
Archive link here: https://archive.is/ikgco https://archive.is/ikgco I’m entirely baffled why someone savvy enough to produce monitoring graphs and claim to already use Cloudflare can be brought to knees by HN (maybe Reddit too or something?) traffic on a frigging blog. I believe you need to actively sabotage your Cloudflare settings to achieve this.
- tazjin 3y ago
  Cloudflare probably respects your cache headers (I haven't used it, but would expect so). This website disables caching in its headers, so Cloudflare can't actually do much.
  - BrandoElFollito 3y ago
    Yes, they should disable caching on index.html only and have the other files update their names on changes
    - acdha 3y ago
      They should allow everything to be cached and use the Cloudflare API to invalidate the cache when they actually change something. That means that even huge spikes will have no impact on their backend and they’ll still be able to see changes within a second or two of publishing them. This complaint is simply an attempt to shift the blame for their decision to ignore multiple decades of prior art. Even in the 90s we used techniques like caching to avoid this problem, and their page-load times now somehow manage to be worse.
      - BrandoElFollito 3y ago
        > Cloudflare API to invalidate the cache This is even better (I do not know Cloudflare that much, but there is indeed the same on AWS' CloudFront)

3 ms·

Ironic that their "please don't share our links" post shared on HN also caused their website to crash. It's a 100% static blog post. Use a damn cache, or CDN, o

by paxys 3y ago

oefrha 3y ago
Archive link here: https://archive.is/ikgco https://archive.is/ikgco I’m entirely baffled why someone savvy enough to produce monitoring graphs and claim to already use Cloudflare can be brought to knees by HN (maybe Reddit too or something?) traffic on a frigging blog. I believe you need to actively sabotage your Cloudflare settings to achieve this.
- tazjin 3y ago
  Cloudflare probably respects your cache headers (I haven't used it, but would expect so). This website disables caching in its headers, so Cloudflare can't actually do much.
  - BrandoElFollito 3y ago
    Yes, they should disable caching on index.html only and have the other files update their names on changes
    - acdha 3y ago
      They should allow everything to be cached and use the Cloudflare API to invalidate the cache when they actually change something. That means that even huge spikes will have no impact on their backend and they’ll still be able to see changes within a second or two of publishing them. This complaint is simply an attempt to shift the blame for their decision to ignore multiple decades of prior art. Even in the 90s we used techniques like caching to avoid this problem, and their page-load times now somehow manage to be worse.
      - BrandoElFollito 3y ago
        > Cloudflare API to invalidate the cache This is even better (I do not know Cloudflare that much, but there is indeed the same on AWS' CloudFront)