Hacker News new | past | comments | ask | show | jobs | submit login

5GB per file.

I mean frontend JS got out of control but I've yet to see bundle.js reach 4.8GB.




That strikes me as small, because CDNs are often used for software downloads and updates. Think Steam, Windows Update, OSX, Xbox Live, PSN, etc, etc. Those files are regularly larger than 5GB.

Obviously those customers have negotiated deals with the CDNs, but if there's a 5GB hard limit it sounds like Cloudflare doesn't want to compete there.

I'm not sure why I'm getting downvoted, I don't think my comment was inflammatory.


Cloudflare has always been different than a generic CDN - their tagline is "The Web Performance and Security Company". Most of their features are focused on those things, and they don't really support video streaming / etc..


Cloudflare has supported video streaming for a while now: https://www.cloudflare.com/products/cloudflare-stream/


I agree with you and it's a mental model that Cloudflare isn't a swiss-army knife CDN.. They optimize for fronting web services (And do that very very well).

I use them on my personal site - but on the corporate side where we need TCP acceleration, edge serving of binary resources and POP presence in China - we turn back to crusty ole Akamai.


For giant files, you can at least break the file up into pieces. If nothing else, it's a greater technical challenge to build a caching system that scales to infinite GB. Why would Cloudflare invest in such a system when it's of dubious utility in the first place?


You can actually use CF cache api in their 'workers' to accomplish this.


If other CDNs do it and cloudflare doesn't, then it's harder to switch.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: