Cloudflare Workers Reviews

I have been using Cloudflare, their CDN services, so we can work with something else other than AWS Lambda within the last 12 months.

I work with Cloudflare Workers.

I have been working with Cloudflare Workers since just last year; we started moving some of the small forms and submissions into Cloudflare Workers.

I am an end-user of Cloudflare Workers, currently as of now.

We are using Cloudflare Workers for quick forms on our website where we collect data about our leads, and those forms get submitted and responded to. We get lead emails through using Workers.

I have found their DB, which is basically Cloudflare Workers, and their deployment solution easier, as well as the way they use the key-value pair, to be the most valuable features of Cloudflare Workers.

These features are particularly valuable to me because it is easy to integrate them into our website and connect to get the data passed.

I have used Cloudflare Workers to enhance web performance.

It has helped optimize user experiences for me by saving a few seconds of load time, as well as for the images, even the form loads, data passing, and all; performance is good, and we save a few seconds of load.

Currently, we are not using Cloudflare's security suite to the level much, as Cloudflare by default provides DDoS support; we are just using Cloudflare's DDoS support, which by default protects against denial-of-service attacks.

I have used Cloudflare Workers' key-value pair for data storage.

It has helped with data access efficiency, especially the data collection of the forms, as key-value pairs are easy to connect, and we are able to validate information much sooner, checking the mobile number.

I assess the execution speed of Cloudflare Workers to be faster, at least providing a 30-40% increase compared to traditional server-based architectures, at a minimum.

I have noticed time efficiency as the best return on investment with Cloudflare Workers; I am not seeing anything else, as time is the major one.

We are planning to integrate WebAssembly with Cloudflare Workers, but we have not done it.

I think we are good with Cloudflare Workers as we were having initial troubles with the ID integration, such as Visual Studio Code, but they have started adding some support when we start using their default packages, which can test locally as well as work in deployment; it is easier now, although the documentation can improve.

I think the pricing of Cloudflare Workers is decent; it is good.

I have used Cloudflare Workers since just last year.

The stability and reliability of Cloudflare Workers have been good, except for a few incidents that happened recently where Cloudflare was down, causing some disturbances very lately, in the last few months.

Because we have not moved fully into production yet, we were okay during these disturbances; we are just testing Cloudflare Workers in our new product which is still in the testing stage, so we are not affected by it, but it did have an impact—it was not working for a few hours, then it came up, then again it failed.

Scalability looks much simpler with Cloudflare Workers, as it connects with Cloudflare's default edge locations; it is actually made for scalability and can work in any edge location supported by the Cloudflare CDN network.

Before Cloudflare Workers, we used traditional server back and DB connection, kind of API-based approaches for these use cases.

We switched to Cloudflare Workers because we were using Cloudflare Zero Trust for internal VPN for quite a long time, and when we tried these Workers, it worked well for us.

We did not have many other options other than Cloudflare; typically, the other option was CloudFront, the CDN support from AWS, but we were using it for some images only and not Cloudflare Workers.

Cloudflare Workers was mostly my first and only choice.

I did participate in the initial setup and deployment of Cloudflare Workers.

During the initial setup and deployment, we used sample packages that Cloudflare provided; we faced some struggles in connecting, testing it locally, and eventually deploying it, but we managed to do it and it was a good experience, very easy; we were able to make our DevOps team start moving to Cloudflare Workers build easily.

I did not face much in terms of challenges during the setup and deployment; there were very minimal integration challenges with IDs, and after that, nothing.

I have noticed time efficiency as the best return on investment with Cloudflare Workers; I am not seeing anything else, as time is the major one.

We did not have many other options other than Cloudflare; typically, the other option was CloudFront, the CDN support from AWS, but we were using it for some images only and not Cloudflare Workers.

I think it is affordable for all types of users, from small to medium-enterprise.

I mentioned earlier that I would prefer to see more documentation on that matter.

The overall positive impact and benefits I have observed since starting to work with Cloudflare Workers have been good; easy testing, setting up, and testing and deployments are much simpler, and the performance is good with faster execution; it appears to be made for the use case that we want, so it is good.

I would rate this review a 9 overall.

We use Cloudflare Workers mainly to avoid Cross-Origin Resource Sharing (CORS) issues and as a reverse proxy. It has also been beneficial in speeding up our application and providing certain data on the edge, particularly sports book betting data.

The most valuable feature of Cloudflare Workers is that the data is on the edge. Since the data is on the edge, it makes the application more responsive worldwide, thus lowering the loading time and increasing user engagement. The scalability of Cloudflare Workers is also impressive, as it can handle spikes of traffic with ease. Cloudflare Workers also contributes to the application being faster and geographically distributed.

Monitoring needs improvement. It's a bit difficult to understand how many failures occur and manage logging effectively.

We have been working with Cloudflare Workers for seven years.

Deploying Cloudflare Workers was relatively straightforward, but there was a learning curve for implementing advanced functions. Initially, it took us about two hours to deploy the smallest part, and we managed this through the Cloudflare portal.

We have never had issues with Cloudflare Workers in production, indicating a high level of stability.

Cloudflare Workers is extremely scalable. It is very important as it helps handle users distributed around the world and spikes in traffic effectively.

While the technical support is generally good, with a rating of seven out of ten, they are not fully familiar with the advanced capabilities of Workers, and there is room for improvement in this regard.

Neutral

We did not use a different solution before adopting Cloudflare Workers.

The initial setup was moderately difficult, with a learning curve for more advanced functionalities. We rated it six out of ten in terms of ease, reflecting some required learning for advanced things but achieving worthwhile results.

One person was enough to handle the initial deployment.

We have seen a return on investment. Cloudflare Workers makes the application faster and more geographically distributed, which enhances the experience for end customers.

Pricing is fair considering the features offered. Our costs vary based on load, with expenses around €100 per month for CORS and approximately €600 per month for using Workers to have data on the edge.

We considered Azure, but remained with Cloudflare due to its DDoS protection and comprehensive security features.

I rate Cloudflare Workers nine out of ten. The solution has been very beneficial for our needs.

Public Cloud

Other

I normally use Cloudflare as a core platform, including CDN solution, WAF solution, and connectivity solutions like web filtering, access, and DTNA solutions. I use Cloudflare Workers only for testing. I use it to put some developments from my site on the platform.

Cloudflare Workers offer integration with GitHub, enabling seamless development and deployment. The platform provides a scalable solution where I can start with a small setup and scale up as needed by paying for the traffic generated. Additionally, it ensures security with minimal latency due to its numerous points of presence.

In general, the security of the product could be improved with minimal latency due to its many points of presence. Additionally, Cloudflare Workers could be enhanced by adding a feature to host virtual machines in the cloud, as this feature is currently unavailable.

Cloudflare Workers is a scalable solution. I can start with a few services and scale the solution according to my needs. The payment is based on the traffic generated, allowing for scaling from a small solution to a large one without issues.

As I am using the free solution, there is no direct support, only access to online documentation.

Negative

I have tested Google as well. Cloudflare is easier to use in my opinion. Google offers many solutions and documentation which makes it more complex to understand. Cloudflare is faster and easier for me, solving problems more quickly than Google.

The initial setup is easy to use. However, I have not explored it deeply, especially with applications and Workers.

I am only testing the solution and have not used the paid version of Cloudflare Workers, so I do not have information on pricing.

I have evaluated Google App as well.

Overall, Cloudflare Workers is a very good solution. I prefer Cloudflare for its speed and ease of use over Google. Cloudflare Workers have an integration with GitHub, which is beneficial. Although I have not tested AI applications, I believe Google's AI options are more mature. I would rate the solution an 8 out of 10.

Public Cloud

Other