I’ve been using Cloudflare for DNS since time immemorial (2017 or so), but for the longest time I didn’t give much attention to their ever-expanding range of other services. Over the past few months I’ve been tinkering with the Workers platform — both at work and in my spare time — and felt compelled to sing its praises.

Use cases

Workers are meant to run lightweight workloads at the edge, which is something one needs to account for when targeting the platform – heavy number crunching and other computatively intensive tasks are better suited for other runtimes.

But what if you just want to run a timed script? Host a lightweight API or a personal website? Serve some files? Workers has your back, and the experience will (probably) be straightforward, frictionless, and cheap.

Value proposal

Cloudflare does not have the deep, plug-into-everything model of the more IaaS focused platforms, but it covers a huge amount of ground without burying you in boilerplate.
The rather impressive toolbox of ready-to-use service bindings includes, among other things:

• KV storage for key/value lookups
• R2 object storage, an S3 competitor with no egress fees
• D1 for SQL databases (disclaimer: I haven’t tried it, might suck) And of course anything you deploy is automatically backed up Cloudflare’s big bad CDN, which alone is a already a huge benefit.

Developer UX

Wrangler CLI is excellent. A capable adult can spin up a “hello world” and have it deployed and accessible on the interent in minutes. The defaults are sensible, and you don’t need to produce hundreds of lines of YAML before you’ve even written a single line of application code.

Local development is equally as smooth. Miniflare is bundled with Wrangler, and runs your Workers locally, while also emulating the necessary service bindings the code might depend on. The overall flow is refreshingly simple: you write some code, run it locally, push it out globally, done.

For a concrete example, I recently rewrote a small personal project to run in Workers.

Pricing

The pricing is almost comically straightforward compared to most other IaaS platforms. The free tier is useful (and in many cases more than enough), but if you outgrow it, the paid plan is five bucks a month. There are obviously limits in the paid plan as well, but in my opinion they are transparent and very generous.

Issues and negatives

First thing that comes to mind is language support. The choices are basically TypeScript, JavaScript, and to a limited extent Python (unless you want to juggle WebAssembly). Then there’s the obvious question of performance: CPU and execution time are capped, and especially in the free tier you can easily exhaust your limits unless you plan ahead.

Another big thing is the platform ecosystem. I mentioned the impressive suite of tools before, but admittedly they are nowhere near as mature as what the large IaaS players like AWS or GCP provide. Debugging can also be a little sparse: logs are serviceable, but without extra tooling the observability is not great.

Finally, the access control and permissions could be more granular. You basically have one single switch that grants a user or API token write permissions to every single worker on the account. Not a huge problem for personal use (although definitely not optimal), but can be a deal breaker in a professional setting.

Final thoughts

I want to make it clear that I’m not getting paid by Cloudflare for this post — I’ve just used the platform a lot lately, and genuinely like it.

The developer UX is impeccable, price is affordable, and while it won’t work for every use case (being more akin to a razor blade than a Swiss Army knife), you should at least consider using it, because it’s great!