Streamlined Security and Fast Load Times: Cloudflare Delivers
August 15, 2024
Streamlined Security and Fast Load Times: Cloudflare Delivers

Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with Cloudflare
In our organization, we are using Cloudflare for multiple purposes such as
1. For Content Delivery as a CDN
2. For DDoS protection and for threat analytics
3. For traffic forwarding using CloudFlare workers
4. For DNS management
5. For Bot management
6. For certificate management
7. For SSL verification
1. For Content Delivery as a CDN
2. For DDoS protection and for threat analytics
3. For traffic forwarding using CloudFlare workers
4. For DNS management
5. For Bot management
6. For certificate management
7. For SSL verification
Pros
- The best part is the content delivery network. Cloudflare has a large network of data centres around the world that helps cache and delivers content quickly to our customers.
- Cloudflare offers us with a fast and reliable DNS service and with the world class features such as Cloudflare workers, SSL verification, certificate management and web application firewall. When all of these are combined together, it provides very strict security for our organization.
- One of the most important feature that we use is the analytics and threat detection. It provides us with the real time insights of all the threats originating from multiple locations and landing on our websites.
Cons
- Over time, I have come to the conclusion that CloudFront is sometimes a little bit slow when it is trying to verify the SSL. We use it on our webpage for SSL verification and when we access it from mobile, we see it takes a little more time for SSL verification.
- Cloudflare's extensive feature set can be overwhelming for new users. When I first worked on it, there were a lot of features shown on the dashboards and I had no idea about those. Streamlining the user interface and simplifying the setup process could help improve the experience for non technical users.
- The pricing for Cloudflare is a little bit complex and sometimes hard to follow.
- We have seen reduced usage and downtimes after using Cloudflare for Caching. This has already yielded ROI as minimal downtime ensures consistent user traffic and increases revenue.
- It can handle significant traffic spikes and shields the website from DDOS attacks. We have prevented a number of DDOS attacks after using Cloudflare and hence we are already seeing an ROI by using it.
- Some of the integrations with Cloudflare are really painful and we have faced a lot of issues because of not having native integrations to certain 3rd party apps.
Overall we are using Cloudflare as well as AWS cloud across various domains in our organization. To some extent such as DNS management on Route53, CloudFront takes advantage of Cloudflare as it provides a straightforward UI for DNS management. But when it comes to traffic forwarding, Cloudflare takes advantage of AWS Route53 as Cloudflare provides Cloudflare workers that have helped us a lot in routing traffic. When it comes to WAF, I think both of them are in tough competition.
The onboarding process was very smooth and convenient. We were able to set up initial DNS records very quickly and proceed forward in working with Cloudflare workers in a month. Regarding CDN, it took at least two months for our dev teams to implement it properly. The documentation was easy enough to understand but the billing is a little bit challenging topic to understand.
Do you think Cloudflare delivers good value for the price?
Yes
Are you happy with Cloudflare's feature set?
Yes
Did Cloudflare live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of Cloudflare go as expected?
Yes
Would you buy Cloudflare again?
Yes

Comments
Please log in to join the conversation