3 ms·

Sounds good. I never encountered any performance issues with Cloudflare. If you have the time for enhancement, then: 1. Option to hit the cache before workers

Sounds good. I never encountered any performance issues with Cloudflare. If you have the time for enhancement, then: 1. Option to hit the cache before workers. (Why we never use workers). 2. Rules for blocking traffic during nights (time-based rules). 3. Make sure every product is a replacement. If you offer the same thing as a cloud provider. Don’t make us write a lot of custom code.

ehPReth 4y ago
Could you expand on 3?
- AtNightWeCode 4y ago
  Why would you swap Azure blob storage or S3 for anything in Cloudflare if it comes with running custom code in workers?
RL_Quine 4y ago
When is night on the internet?
- AtNightWeCode 4y ago
  Not uncommon before the intro of edge services to block login on sites during off working hours or during nights. Or at least doing some rate-limiting. We see many attempts at brute force-attacks during the nights. Most sites are not global.
- yamtaddle 4y ago
  Most—maybe damn near all—sites see significant dips in traffic for at least a few hours a day. Which part of the day, depends on the site. More often than not, it's while the team is asleep and staffing, if any, is at its lowest point, since teams tend to live roughly in the same ~half of the world that their products are most-used in. Plus there's practically no-one in the Pacific until you reach Japan, and not a ton of "Western" sites see much use in Asia, and vice versa, with a few notable exceptions. It's not unusual for e.g. ecommerce sites to crank up automated fraud prevention "at night" because staffing is so much lower. TL;DR Most sites' usage patterns exhibit a pronounced day/night cycle that's not too far off from natural day/night cycles where the bulk of the team lives.
  - karambahh 4y ago
    Fraud prevention or even straight up order blocking between 1:30 & 4AM because the downstream order management system has only so much buffer capacity (it's getting rarer, but it does still happen. Fraud prevention cranked up is definitely a thing on any large enough ecommerce website)
zwily 4y ago
I agree with #1... Workers before the cache is crazy powerful for the original purpose of Workers (modifying incoming requests). But now that people are starting to use Workers as their original (for remix, etc) it would be nice to be able to have the cache before Workers. As it is right now, having the CDN do full content caching of rendered Remix pages is difficult.

ehPReth 4y ago

Could you expand on 3?

AtNightWeCode 4y ago
Why would you swap Azure blob storage or S3 for anything in Cloudflare if it comes with running custom code in workers?

RL_Quine 4y ago

When is night on the internet?

AtNightWeCode 4y ago
Not uncommon before the intro of edge services to block login on sites during off working hours or during nights. Or at least doing some rate-limiting. We see many attempts at brute force-attacks during the nights. Most sites are not global.
yamtaddle 4y ago
Most—maybe damn near all—sites see significant dips in traffic for at least a few hours a day. Which part of the day, depends on the site. More often than not, it's while the team is asleep and staffing, if any, is at its lowest point, since teams tend to live roughly in the same ~half of the world that their products are most-used in. Plus there's practically no-one in the Pacific until you reach Japan, and not a ton of "Western" sites see much use in Asia, and vice versa, with a few notable exceptions. It's not unusual for e.g. ecommerce sites to crank up automated fraud prevention "at night" because staffing is so much lower. TL;DR Most sites' usage patterns exhibit a pronounced day/night cycle that's not too far off from natural day/night cycles where the bulk of the team lives.
- karambahh 4y ago
  Fraud prevention or even straight up order blocking between 1:30 & 4AM because the downstream order management system has only so much buffer capacity (it's getting rarer, but it does still happen. Fraud prevention cranked up is definitely a thing on any large enough ecommerce website)

zwily 4y ago

I agree with #1... Workers before the cache is crazy powerful for the original purpose of Workers (modifying incoming requests). But now that people are starting to use Workers as their original (for remix, etc) it would be nice to be able to have the cache before Workers. As it is right now, having the CDN do full content caching of rendered Remix pages is difficult.