Cloudflare, from the company of the same name in San Francisco, provides DDoS and bot mitigation security for business domains, as well as a content delivery network (CDN) and web application firewall (WAF).
$20
per month
Fastly Edge Cloud Platform
Score 8.0 out of 10
N/A
Fastly, headquartered in San Francisco, offers the Fastly Edge Cloud Computing, Content Delivery Network (CDN) (formerly Fastly Deliver@Edge). Priced by bandwidth in gigabytes and number of file requests, Fastly supports image optimization, video and streaming, load balancing, and cloud security via web application firewall (WAF) and DDoS protection. Additionally, Fastly is available as a managed CDN.
Cloudflare is the best option for my business for my use cases aligns exactly with what Cloudflare provides. Fastly only offers 1 month of free trial while AWS Route 53 is heavily integrated with AWS cloud. I want the flexibility to launch my own VPS and have a CDN, DDoS …
In my opinion it is the best one to manage and has a lot of resources written for you to be able to grasp any concept that you might need help in. It is a tool that you can handle alone if you have the basic knowledge.
Cost-efficient and easy to use. Developer-friendly, unlike Fastly which is very complex to use. Several products combined in the same offering making it a single tool to solve several problems like CDN, Image Management, DDOS Prevention, Smart Network Routing.
CloudFlare shines in a situation where you need a low-cost solution that can be un-integrated with other aspects of your deployment. For websites that have larger DDoS risk, their DDoS solutions are also attractive. Up-market, their enterprise offerings are on par with services …
It is easy to set up, and within 10 minutes it is up and running. You can add many domains in one dashboard. So no need for a separate Cloudflare account. I can access all my domain DNS, and customize/add it further. For example by adding the Google Webmaster DNS key or my email provider.
The service is really well-suited for pretty much any site that is primarily display-driven (that is, mostly GET requests). The network is able to handle massive volumes of traffic and their POPs have spread out pretty much anywhere that it's easy to get them (so basically everywhere but China and Russia). My team witnessed several large-scale attack attempts on some high-profile websites (attacks in the 10s of millions of requests per second) that were mitigated before ever coming back to the actual application; in one case we didn't realize the attack had happened until we looked at the logs the next day. Because it's a cache store option, the default configuration does not cache POST responses, and it can be difficult to set up things like authenticated paywalls as a result.
Registrar and DNS services are impeccable, with registrations done at cost and without ADs. DNS services setting standards for speed of resolution.
DDOS protection. With their content distribution network to back them they have the bandwidth and tools to be both proactive and reactive to bad actors.
WAF - Their Web Application Firewall helps mitigate common site vulnerabilities and has active zero-day protection running for breaking exploits
In some cases, using Cloudflare can actually lead to slower website speeds if the network is congested or if the website's traffic is particularly heavy.
Some website owners may find that the level of customization offered by Cloudflare is limited, especially in comparison to other solutions.
While Cloudflare is easy to set up and manage, it may be too complex for users who are not familiar with web technologies.
Everything is extremely concise and all settings apply immediately and take effect globally. There is no reason to explicitly plan/think in terms of individual regions as one would have to traditional cloud offerings (AWS, OCI, Azure). All Cloudflare products integrate seamless as part of a single pipeline that executes from request to response.
We really like to talk to a person on the phone or using chat. But the system is very slow and sending to much email to get the issue solve. Something we don't like to spend time writing on the community forum our issue because we don't want to share detail information of our POC.
Firebase can be a good starter for basic projects but as I scaled up, I found it lacking the maturity Cloudflare has. Naturaly, I opted for Cloudflare for bigger projects. I still use Firebase, but for small scale hobby projects only.
A lot of requests are cached and so egress costs from downstream providers are mitigated.
DDoS protection has also managed to keep our site up and our cloud computing bill down.
Setting up a proxy with a worker made putting various Google Cloud Functions running behind a single URL very easy and performant. Plus they offer API Shield on top of this.