It’s quite frustrating as a Cloudflare fan to read many of their blog posts and just not understand what they are promoting.<p>This post is an example, where I’m a developer, I just want to get to the concrete nuts and bolts. But we start off at a very high level, the problem often sounds a bit generic, and then it zooms into an example I just don’t get, I don’t have anything to compare it to or a concrete, real world example.<p>I don’t know if the Cloudflare blog has an editor, but I feel it needs one. There’s a lot of posts and I feel I have to trawl through to find the nuggets. The actual work that is produced is great, I just often don’t get how it is told through the blog.
It just seems to be a management platform to allow you to deploy and track the runtimes of an unlimited number of Workers (i.e. functions) that operate in a tenant-isolated manner.<p>This is surprisingly easy to do with AWS Lambda right now, even though you need to understand the security implications and mitigate them to make this work safely. You just have to look at the Twilio functions implementation to see how someone achieves this at scale today. But having a prebuilt solution designed specifically for this is promising.<p>It's a good idea though, but yet another blog article with no info on pricing and the only way to access it is by going to Cloudflare cap-in-hand to ask politely. Who knows when (or if) this will ever become publicly available or be cost-effective long-term.
So each user of my SasS can have its own set of scripts? How big can each one of these scripts be? Can this script run wasm like normal workers? Can I embed data in it, like a serialized sqlite?<p>How fast is the startup of these scripts? Is it like a Cache read or more like a KV Store read?
"To get started, we ask that you fill out our form, and we’ll get in touch with you."<p>Yeah how about no. They pulled the same nonsense with R2 storage. Unless you're a known enterprise user, nobody is going to reply.