Cloudflare Workers Reviews & Insights

We were facing several problems in our organization; we did a bit of research on how to solve them, and then finally we found Cloudflare Workers. I just want to mention two cases where Cloudflare Workers has helped us.

First, it was very difficult for us to manage extensive URL redirections, but after using Cloudflare Workers, we became able to implement a large-scale URL redirection strategy. Fortunately, this reduced our manual efforts and saved a lot of time.

The second problem we were facing was managing a huge number of emails we were receiving. We use the Cloudflare Workers in combination with mail channels to manage email traffic; absolutely, this helps us a lot.

There I want to mention three areas where Cloudflare Workers is well suited.1. Its bulk URL redirection is extremely beneficial.2. Its email service optimization helps a lot every business or organization that receives a huge number of emails.3. Its edge caching assists website owners in dynamic content caching.

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.

Good: really best in breed for lambda on the edge. it's much easier to make complex redirects decisions in JS rather than using rewrite rule syntax
Good: wrangler CLI for local development

Bad: no built-in retentions of logs and it's still hard to troubleshoot issues on the edge