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

Honest question: Why is everyone pushing CentralizedFlare pro so hard in this thread?



Cause it solves real issues for dirt cheap....

I mean really cold cache from the above user is at 5000ms that's pretty horrible. When I tried I got 2800ms. Take a look around it seems to be mostly from fetching static content which is a classic problem CDNs solve.


> Cause it solves real issues for dirt cheap...

One doesn't even need pro. In our use, Cloudflare's pages.dev and workers.dev serves single-digit TB traffic with triple-digit million hits at $30/mo. We pay $0/mo for origin servers since there aren't any.


Unique Visitors 358.45k, Total Requests 22.13M, Total Data Served 3 TB from cloudflare + a scaleway stardust for 1$ per mo.


IPv6 only stardust I am guessing?


Got it, yeah, web-tier caching is annoying to do yourself. Cheers and thank you kind sir or madam!


It doesn't have to be annoying, just easier.

People have been citing $30/month. Even if you value your time at min wage, its probably still cheaper than setting up your own varnish (and that's assuming you don't care about improving the last little bit of latency with geo located edge servers)


Can we not call companies silly names. It seems childish.

To answer the actual question - its the obvious answer. They make a product that works well and is relatively cheap. Is it without drawbacks? obviously not, nothing is. However, for a significant segment of the market the value proposition makes sense.


Is there a decentralized solution you would recommend that’s better?


I appreciate you are replying to someone, but i feel like this doesn't quite make sense. You're running a website. Why would your web server be decentralized? HTTP is a client/server protocol after all.


Because caching is part of the HTTP spec. If content doesn't change on every request, you cache it with a timeout. If users are looking at your site from around the world, you want the cache to exist as close to them as possible. This is the job of the CDN. In Cloudflare's case, they sit between your web server and the user and can be that HTTP cache. If your site is popular, you might still have multiple versions of it across regions.


Because the linked article is about Cloudflare? It's like asking why a comment thread on an article talking about apples is discussing apples. Or are you asking why so many people are _pro_ Cloudflare?


It happens to be a big bullet point in TFA, so it appears in discussions of TFA, duh.


Because many competitors have taken an "Enterprise focused" approach. The choice of CDNs for more than media hosting and without $$$ commitment is quite small.


What would you propose as an alternative?


AWS CloudFront


Cloudfront's bandwidth pricing is outrageously high at $0.08/GB (up to $0.12/GB for some regions). Meanwhile, Cloudflare doesn't even charge for bandwidth.




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

Search: