Likelihood to Recommend Experienced a lack of available programming languages while working on a minor project. I had to halt the project and wait for it to be added later. It took ages and had a hit on our productivity. It has a centralized management system which helps and an easy interface which helps to manage multiple tasks in case of large-scale operations and projects.
Read full review 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.
Read full review Pros API Gateway integrates well with AWS Lambda. This allows us to build a web server in the language and framework of our choice, deploy it as a Lambda function, and expose it through API Gateway. API Gateway manages API keys. Building rate limiting and request quota features are not trivial (or interesting). API Gateway's pricing can be very attractive for services that are accessed infrequently. Read full review 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 Read full review Cons Client certificates are troublesome when trying to attach them to API GW stages. Debugging across several services can be difficult when API GW is integrated with Route 53 and another service like Lambda or EC2/ELB. Creating internal/private APIs, particularly with custom domains, can be unintuitive. Read full review 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. Read full review Likelihood to Renew lower cost
Read full review Usability 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.
Read full review Reliability and Availability In 6+ years of relying on Cloudflare, I think we experienced one or two brief outages that were Cloudflare's fault.
Read full review Performance Their Argo for the global network is the core feature we love.
Read full review Support Rating We always had a great experience with the AWS support team. They were always on time and very dependable. It was a good partnership while we worked to resolve our issues.
Read full review 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.
Read full review Implementation Rating Very well executed implementation where our team was able to handle the implementation with guidance.
Read full review Alternatives Considered When we tested
Azure API Management at the time, it had serious connectivity issues, it was very unstable, and it needed to do a lot using the command line. Comparing with the AWS solution, which was more mature, and the fact that we have services in use on AWS, we ended up choosing to continue using AWS products. This so as not to run the risk of increasing latency in accesses, and of some functionality not working, due to being developed yet.
Read full review 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.
Read full review Scalability They are built for scale and have the capacity to handle all the traffic we could ever expect to get.
Read full review Return on Investment ROI is negative, you need either to hire them to work with you or spend days/weeks to figure out issues. For some of the projects in the end it is not worth it, it is just a "buzz" to use serverless but not practical. Service is easy to set up authorization and it is easy to manage. Read full review 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. Read full review ScreenShots