What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
Monitoring needs improvement. It's a bit difficult to understand how many failures occur and manage logging effectively.
For how long have I used the solution?
We have been working with Cloudflare Workers for seven years.
What was my experience with deployment of the solution?
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.
What do I think about the stability of the solution?
We have never had issues with Cloudflare Workers in production, indicating a high level of stability.
What do I think about the scalability of the solution?
Cloudflare Workers is extremely scalable. It is very important as it helps handle users distributed around the world and spikes in traffic effectively.
How are customer service and support?
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.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We did not use a different solution before adopting Cloudflare Workers.
How was the initial setup?
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.
What about the implementation team?
One person was enough to handle the initial deployment.
What was our ROI?
We have seen a return on investment. Cloudflare Workers makes the application faster and more geographically distributed, which enhances the experience for end customers.
What's my experience with pricing, setup cost, and licensing?
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.
Which other solutions did I evaluate?
We considered
Azure, but remained with
Cloudflare due to its DDoS protection and comprehensive security features.
What other advice do I have?
I rate Cloudflare Workers nine out of ten. The solution has been very beneficial for our needs.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
*Disclosure: My company does not have a business relationship with this vendor other than being a customer.