Earlier quoted context omitted.
This is not accurate. I do not know the details but netlify served things from a CDN by default if you set things up correctly with a CNAME entry in your DNS record. People often misconfigure things by pointing their domain to netlify's IP with an A entry, but this is a user problem, not a netlify problem. I'm sure their builds/functions run in a single region but not static files
Based on my limited knowledge, you have to point your root domain (e.g. example.com) to their IP address because it’s an A record. For the a CNAME record (e.g. wwww) it can be pointed to their CDN. I think if you use Netlify DNS for your domain, then you can point A records to their CDN because it’s an alias at that point. Like, A record aliases on AWS Route53.
Switching to BunnyCDN in Less Than 2 Hours
71–73 of 73 posts
Re: Switching to BunnyCDN in Less Than 2 Hours
#72It will be fascinating to see if the protectionist foreign policy that's been adopted by the US will lead to an improvement in the quality of services available elsewhere. Previously, the friction of using a service with slightly rougher edges would have tipped the scales against it. Now, it seems we have a kind of patriotism emerging in our purchase decisions. Ultimately, it should give us all more choice through st…
Bunny doesn’t have a ton of rough edges to begin with, but I do have some easily addressed pet peeves here and there.
I’ve heard of a few US tech businesses voting for stability with their wallets and shifting to foreign service providers because of the instability here in the states. Some regulated industries will not have that luxury of course.
Re: Switching to BunnyCDN in Less Than 2 Hours
#73Earlier quoted context omitted.
Yeah but it’s like using a EU vendor that hosts on AWS, if the US government wants the data they’ll just subpoena AWS instead of the EU provider. I get that it’s better but anything hosted on US soil is under jurisdiction of the US government regardless of whether it’s ultimately owned by a EU vendor.
An EU vendor with their own hardware or using an EU provider underneath then it’s very different to an EU provider using AWS underneath
I used to consult for a Canadian firm. Their sales folks complained that prospective accounts from outside the US would often include in their negotiations something to the effect of “you need to service our account through a non-US entity.” This firm had no non-Canadian entity.
But it was a very well known tech firm, so the assumption was that it was American.
Turned out the objections from prospects got a lot more strenuous (read: deals from non-US prospects not closing) when the firm’s cloud services were only available through AWS in the US.