If you host on Cloudflare Pages, does enabling Argo have any benefit?
CloudFront vs. Cloudflare, and how to reduce response times for both (2021)
11–20 of 57 posts
Re: CloudFront vs. Cloudflare, and how to reduce response times for both (2021)
#12Now that CloudFront has greatly improved its performance, what's the pitch for using CloudFlare over it?
Price is the main difference between AWS CloudFront/Fastly and CF. In most cases, CF prices are fixed, like $200 for business or $20 for the pro plan. If you like fixed prices VMs from Linode or DO, chances are high that you will like Cloudflare too. Of course, advanced addons features like CF Argo and CF Bot management cost more money at Cloudflare too.
While that lasts, you can't be charging a flat $200 in a world where the other players are charging 5-10¢/GB of egress.
Re: CloudFront vs. Cloudflare, and how to reduce response times for both (2021)
#13Now that CloudFront has greatly improved its performance, what's the pitch for using CloudFlare over it?
The numbers of zeros after the dot/comma (depending on your locale)
Re: CloudFront vs. Cloudflare, and how to reduce response times for both (2021)
#14Earlier quoted context omitted.
Price is the main difference between AWS CloudFront/Fastly and CF. In most cases, CF prices are fixed, like $200 for business or $20 for the pro plan. If you like fixed prices VMs from Linode or DO, chances are high that you will like Cloudflare too. Of course, advanced addons features like CF Argo and CF Bot management cost more money at Cloudflare too.
While that lasts, you can't be charging a flat $200 in a world where the other players are charging 5-10¢/GB of egress.
Alot of the companies who bought cloudflare would probably rather pay the 200$ than deal with migrating everything.
Re: CloudFront vs. Cloudflare, and how to reduce response times for both (2021)
#15TLDR, adding an "edge" in front of your application incurs a connection setup cost which can be 2-3x RTT and is especially noticeable when you don't have a large QPS and are in a region like APAC where geographically close networks often have high latencies between each other. Both Argo and OriginShield seem to pool more aggressively, often going cross-datacenter to avoid hitting origin which sometimes saves this setup cost by coalescing onto warm connections, but only sometimes (notice how spiky their Argo graphs are, the p90 request is probably no faster than before).
Re: CloudFront vs. Cloudflare, and how to reduce response times for both (2021)
#16Earlier quoted context omitted.
Wanna bet? https://www.buzzfeednews.com/amphtml/johnpaczkowski/amazon-p... https://amp.theguardian.com/media/2010/dec/01/wikileaks-webs... Etc etc…
Except for the fact that hosting Wikileaks and Parler with the content in question was always legally contentious. What Kiwifarms or The Daily Stormer hosted was sufficiently odious (in my view at least), it is disingenuous to suggest that the content is at the same level as what Amazon took action against.
So why aren't those sites on Amazon right now? Seriously, if Amazon is such an amazing bastion of allowing that disgusting content, why are KiwiFarms and the Daily Stormer not happily up and running on AWS with CloudFront?
Re: CloudFront vs. Cloudflare, and how to reduce response times for both (2021)
#17Now that CloudFront has greatly improved its performance, what's the pitch for using CloudFlare over it?
No post body was provided.
Re: CloudFront vs. Cloudflare, and how to reduce response times for both (2021)
#18Earlier quoted context omitted.
Wanna bet? https://www.buzzfeednews.com/amphtml/johnpaczkowski/amazon-p... https://amp.theguardian.com/media/2010/dec/01/wikileaks-webs... Etc etc…
Except for the fact that hosting Wikileaks and Parler with the content in question was always legally contentious. What Kiwifarms or The Daily Stormer hosted was sufficiently odious (in my view at least), it is disingenuous to suggest that the content is at the same level as what Amazon took action against.
All of those sites are toxic customers. Continuing to host them will draw the government's ire.
For Parler, the Jan 6 Committee would have inundated Amazon with subpoenas for internal documents and demanded testimony from executives. It's understandable why Parler was deplatformed so many times: because nobody likes government scrutiny. The risk is clearly greater than the reward.
I'm not saying that this was the right decision for society, but I understand where they're coming from, and these companies should be transparent about their motivations.
Re: CloudFront vs. Cloudflare, and how to reduce response times for both (2021)
#19Earlier quoted context omitted.
Except for the fact that hosting Wikileaks and Parler with the content in question was always legally contentious. What Kiwifarms or The Daily Stormer hosted was sufficiently odious (in my view at least), it is disingenuous to suggest that the content is at the same level as what Amazon took action against.
So why aren't those sites on Amazon right now? Seriously, if Amazon is such an amazing bastion of allowing that disgusting content, why are KiwiFarms and the Daily Stormer not happily up and running on AWS with CloudFront?
No post body was provided.
Re: CloudFront vs. Cloudflare, and how to reduce response times for both (2021)
#20If you host on Cloudflare Pages, does enabling Argo have any benefit?
No, Argo optimizes the route of traffic from the edge (your closest Cloudflare data center) to the origin (the server hosting your website). With Pages, everything is served from the edge.