CherryJimbo

The Cloudflare Discord is interesting. It's mostly maintained by community volunteers (Champs and MVPs), with team participation varying drastically from team to team. The community does a great job when they can, but it doesn't feel like most teams are empowered to help people there. There are some fantastic employees who do help regularly though, but as far as I know, most employees are doing this out of kindness, since it's not actually part of their role (whether Cloudflare should make this a part of some folks roles is definitely something they should think about heavily).

The best way in Discord is to post in a forum channel like #pages-help or #general-help. There's tooling the community has to actively monitor and reply to those, vs a fast-moving text channel where things can be buried quickly. This is one of the reasons Discord isn't a great platform for offering support.

Community Champs / MVPs have the ability to escalate some things, but posting on HN will always get more attention. We've been raising issues around some things that are impacting lots of people every single day (wrangler.toml + Pages config breaking projects regularly for example), but if you want something fixed quickly, making some noise on social media is always going to be the quickest way, sadly.

You would almost certainly have to be paying for an ENT agreement before you got anywhere close to 300PB of traffic, which would incur bandwidth fees.

It'd still be significantly less than $27 million though.

This is seriously cool. From Twitter (https://twitter.com/KentonVarda/status/1178723944007733251):

> Not only does this use (much) less overall CPU and RAM, but it avoids delaying TTFB. Also elements you want to modify are selected using CSS selector syntax which makes things nice and easy. It may seem like a small thing to some but I'm pretty excited about this.

Previously I was doing things like fetching content, running some regex replaces, and then returning the changed content. Being able to do this dynamically and in real-time without delaying TTFB is incredible.

If you're not familiar with Backblaze, they offer personal backup services at very affordable rates, but their best offering (in my opinion) is their B2 Cloud Storage (https://www.backblaze.com/b2/cloud-storage.html). It's essentially like Amazon S3, but at a fraction of the cost. If paired with Cloudflare and the Bandwidth Alliance (https://www.cloudflare.com/bandwidth-alliance/), egress is entirely free too, meaning that you only pay for storage and API requests.

Their biggest limitation to date has been that they're only in the US, but today they launched their first EU data center in Amsterdam!

I'm a heavy user of Backblaze both personally and in my company, and you can check some of these blog-posts for use-cases and more info:

- https://blog.jross.me/free-personal-image-hosting-with-backb...

- https://nodecraft.com/blog/development/migrating-23tb-from-s...

You get 100,000 requests per day, not per month. The burst limits are definitely a concern for heavy traffic, but for just $5 you can remove the burst limits entirely, as you mention.

That was entirely my bad. I was moving a few things around.

And compresses them heavily.

Workers are also used for basic CORS headers, and stripping some other unnecessary headers. They're definitely not required, but I don't believe you can do URL rewriting with page rules; redirects, sure, but not rewriting.

It's entirely free if you only use the Cloudflare-routed URLs thanks to the Bandwidth Alliance: https://www.cloudflare.com/bandwidth-alliance

You're very welcome - I'm glad it was helpful. B2 is significantly cheaper than S3, especially when paired with Cloudflare for free bandwidth. If you're interested, my company Nodecraft talked about a 23TB migration we did from S3 to B2 a little while ago: https://nodecraft.com/blog/development/migrating-23tb-from-s...

As others have said, bandwidth costs can be absolutely insane with AWS. This was actually the primary reason we moved from S3 to Backblaze B2 as documented at https://news.ycombinator.com/item?id=19648607, and saved ourselves thousands of dollars per month, especially in conjuncture with Cloudflare's Bandwidth alliance. https://www.cloudflare.com/webinars/cloud-jitsu-migrating-23...

We still use AWS for a few things and still have a small bill with them every month, but we're very careful about putting anything there that's going to push a lot of traffic.

Sure, but my point doesn't change. https://scotthelme.co.uk/the-power-to-revoke-lies-with-the-c... is a good write-up about that.

Browsers are moving away from showing differences between EV and DV certs nowadays though. And anyone can register a company name and get an EV cert - that doesn't make it trusted. https://stripe.ian.sh/ is a prime example of this.

HTTPS is a nice reassurance, sure, but an EV cert isn't.

We had to pick something that was "good enough" for compression time/size, as well as easy for our customers to download/view if they wish, on any OS. Zip being supported in every popular operating system, and the average user using Windows being able to right click -> unzip, was the primary reason for choice.

There are of course significantly faster and more efficient compression formats like LZ4 which would be ideal if we were solely using the data internally in managed environments, but we offer these backups as downloads to our users, some of which aren't very technically inclined and still need to be able to access the files easily.

I can't speak for Cloudflare, but we've talked to them pretty extensively about the whole project, and even did a case study about our use-case with the bandwidth alliance, and as we switched cloud providers. Things may change in the future of course, but they very much encouraged what we were doing. https://www.cloudflare.com/case-studies/nodecraft-bandwidth-...

They're "backups" in the sense of storing customer data, but realistically they're more like instance snapshots for various customer game servers. They're created and restored multiple times a day for every customer as they hop between games (accessed very frequently), so Glacier wouldn't be a good fit.

We do use Cloudflare, but a lot of the instance backups we store are multiple GBs - Cloudflare doesn't cache those. Not to mention uploads from regions like Singapore can be very slow all the way to the US.

It's not a deal-breaker for us, but we're very much looking forward to when they can support more regions.

We looked briefly at the snowball and fireball, but wanted to do this as quickly as possible, whilst keeping the process entirely transparent to our users. It was also an excuse for our team to get intimately familiar with the B2 API, since it's not compatible with S3.

If we were to consider another large migration like this, physical media would probably be the way to go.

We did not. Wasabi looks interesting - thanks!

Almost double that, as we didn't hit the tier for the lower $0.05 pricing. We also used some of their more expensive locations for some storage too, like Singapore - the 23TB was spread between different regions.

Unfortunately... yes. They have Europe coming "really soon" when we were talking to them which we're excited about, but it's one location in the west coast of the US currently.

You're absolutely right - there's nothing stopping a standard MySQL setup pulling off the same stats, but it just wasn't what we were looking for, coupled with the various other decision points made in the post. RethinkDB's native ability to shard and scale is the key performance case to be made, in my opinion.

As mentioned by another user though, the filtering here is done entirely server-side (at RethinkDB's level), so the V8 thread performance isn't really a concern. https://news.ycombinator.com/item?id=9411738 for more info.