The real advantage of cloudflare workers is you don’t pay for the processing time while you’re waiting for upstream network responses.

I believe Cloudflare is the only FaaS that offers that. It makes it fantastic for putting a light weight layer in front of a few upstream API, like say inference providers.

Isn't this a move in the other direction. Workers and traditional Lambda need to you write short lived event handlers; this is about running a standard server.

Google Cloud Run and Azure Container Apps feels like the closest analogues.

Both allow deployment of web apps without an adapter layer. Both scale to zero (really useful for hobby apps; small internal apps that do not get sustained traffic, but can get bursty). Both allow concurrency control.

Cloud Run "family" is quite a nice way of managing serverless ("orchestrationless"?) containers. Cloud Run worker pools for background workers that connect to Pub/Sub. Cloud Run jobs for long running tasks like extracts, ETL. Cloud Run instances (newer offering) for always on agents.

Absolutely, and the offer is better in terms of DX (no need for an adapter) and it’s not limited to 128MB of memory.

Exciting times, I can’t wait for Cloudflares response.

but this is built on firecracker vm. while Cloudflare workers are built on v8 isolates. at the moment Cloudflare workers have no equivalent. Deno was the only one trying to do the same.

what will be interesting to see is startup times.

Also vercel, railway, render etc

Cloudflare workers wasn’t always an 1:1 option for simple hosting (iirc) and people used to think it was more complicated than vercel etc but it has changed in recent years and right now they have made things smoother and simpler to compete with vercel and others.

Now that AWS has entered into the field as well, given that vercel and others already build on top of AWS. It will be interesting to see how this all goes.

I wonder if more og hyper scalers like say hetzner/ovh and others will also target this audience

And appengine