top | item 43178186

(no title)

aroman | 1 year ago

Lol - it's not that Cloudflare can't handle the traffic. It's the _framework_ can't handle the traffic and set up Cloudflare to ratelimit entry using their Waiting Room[0] product.

Clearly poorly messaged if it made you think it was a Cloudflare capacity issue!

[0] https://www.cloudflare.com/application-services/products/wai...

discuss

order

rkagerer|1 year ago

WTF indeed, Framework. The whole point of a CDN is to keep your website operational when the number of visits scale up. A "waiting room" might as well be a 404.

Here's a screenshot of https://frame.work/ca/en/blog/category/news:

https://i.imgur.com/7BcLyCX.png

There's nothing up there that couldn't be statically cached.

frosting1337|1 year ago

Except, you know, the entire dynamic functionality of purchasing everything. Taht can't be cached.

ed_mercer|1 year ago

This is weird. You can’t handle the load of a planned announcement on your landing page, in 2025? Something tells me their CTO role could use a new hire.

winrid|1 year ago

Quite funny as one of these desktops could likely handle the traffic :)

lionkor|1 year ago

Not when every second line of code in the framework (haha) used really boils down to 250 calls and abstractions, when most of it is probably just strcpy()