3 ms·
> We can’t think of any good reason to do without [CDNn] CDNs are another way to track everybody. So privacy is an excellent reason for not using a CDN.
by sunshine_reggae 3y ago
> We can’t think of any good reason to do without [CDNn]
CDNs are another way to track everybody. So privacy is an excellent reason for not using a CDN.
- dmurray 3y agoIt's also an extra point of failure, an extra account to manage, etc. I have seen plenty of low-traffic Rails (and other) apps where neither hosting cost nor performance would be significantly improved by adding a CDN.
- c0balt 3y agoOr simpler, why do you need a CDN? It's rarely worth the additional work (setup + deployment) when most websites are not limited by bandwidth for assets.
- vemv 3y agoIf you're serving assets directly from S3 (or even from nginx) you're exposed to a "denial of wallet" attack, given the price markup on outbound networking.
- __s 3y agoYou're answering "Why do you need CDN?" with "Because I'm on AWS" Their point stands: if you don't have a reason to use a CDN, don't use a CDN
- zelon88 3y agoSo you have 10 scripts on your page, and you put them in 5 different hosts. What does the waterfall on that look like? You're probably talking about a web app that transfers 2.6mb to the user who only wants to read 78 bytes of text. And your primary concern is the markup on outbound networking? Don't design crap pages and outbound networking isn't a problem. Most of the data transfer is fluff nobody wants or needs anyway. You built the website! Now you don't think it's worth sending to the user? Or did you maybe go overboard when you were adding things to it?
- jon-wood 3y agoI'll add cache invalidation to the list of reasons not to use a CDN. Its a solvable problem, but I've more than once seen irritating issues caused by something getting cached in the CDN layer and loading the wrong resources.