5 ms·
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 Wait
by aroman 2y 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/waiting-room/ https://www.cloudflare.com/application-services/products/wai...
- winrid 2y agoQuite funny as one of these desktops could likely handle the traffic :)
- lionkor 2y agoNot 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()
- rkagerer 2y agoWTF 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://frame.work/ca/en/blog/category/news: https://i.imgur.com/7BcLyCX.png https://i.imgur.com/7BcLyCX.png There's nothing up there that couldn't be statically cached.
- frosting1337 2y agoExcept, you know, the entire dynamic functionality of purchasing everything. Taht can't be cached.
- rkagerer 2y agoThat would be a sensible place to use a queue, too bad it's not constrained to there. I'm not familiar with how granular the CloudFlare feature is - could they have enabled it only for a portion of their site like https://frame.work/marketplace https://frame.work/marketplace? Otherwise, could be a good reason to use subdomains when architecting sites, say shop.framework.com.
- ed_mercer 2y agoThis 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.