Overall Satisfaction with Cloudflare Workers
Cloudflare Workers have very powerful but at the same time simple enough API. They comes really handy when you need some computational power on the backend, but for some reason having a separate service seems like an overkill.
One of the use-cases we embrace is to optimize page loading of our site: proxying request to reduce DNS resolve time & prefetching/preloading and even parallelization of the loading for some critical resources.
One of the use-cases we embrace is to optimize page loading of our site: proxying request to reduce DNS resolve time & prefetching/preloading and even parallelization of the loading for some critical resources.
- Proxying
- Html rewriting
- simple storage on the edge
- monitoring - no build-in way to have retention for logs
- service binding - is not well supported for the local development.
Do you think Cloudflare Workers delivers good value for the price?
Yes
Are you happy with Cloudflare Workers's feature set?
Yes
Did Cloudflare Workers live up to sales and marketing promises?
Yes
Did implementation of Cloudflare Workers go as expected?
Yes
Would you buy Cloudflare Workers again?
Yes