It's true that, at least at present, Cloudflare Workers is primarily meant to implement web application servers. There are obviously many other ways people use

It's true that, at least at present, Cloudflare Workers is primarily meant to implement web application servers. There are obviously many other ways people use servers which Workers does not yet address. I don't think the post was intended to mislead people into thinking Workers serves those other use cases well today (or 4 years ago, when it was written). Rather, I think Zack just wasn't thinking about batch work as he wrote. When you spend all your time focused on one problem space, it's easy to forget that others exist. With that said, I do think the Workers architecture will be a great fit for batch work when we get to it. The reason being, infrastructure for batch work is often all about bringing the code to the data, rather than bringing the data to the code. Workers is extremely good at running code in whatever location is ideal, in extremely fine-grained units. Yes, supporting only JavaScript and WebAssembly will be a limitation, but I suspect the advantages will outweigh the disadvantages. But again, we haven't had the chance to focus on that yet. If you're doing heavy batch work today, Workers probably isn't the best place for it. Yet. (Disclosure: I'm the tech lead for Workers.)