At this point they're competing with CloudFront, S3, and Lambda, but it is still a a long ways away from all of AWS.

> * At this point they're competing with CloudFront, S3, and Lambda, but it is still a a long ways away from all of AWS. *

Cloudflare's offering does not compete with Lambda at all. They have completely distinct usecases.

Cloudflare Workers at best compete with Lambda@Edge, which in spite of its name is actually a CloudFront feature.

https://aws.amazon.com/lambda/edge/

Cloudflare Workers competes with both Lambda and Lambda@Edge. Workers is a general-purpose compute platform that happens to run on the edge; it is not a platform intended to be specific to things that need to run on the edge.

(Disclosure: I'm the tech lead of Workers.)

It's probably better said as, "CF Workers competes with Lambda's synchronous use-cases".

Based on what I understand, there are still a few things missing to compete with Lambda's asynchronous use-cases. e.g. Step Functions, 15 min time limits, non-cron events (i.e. events for every CF product), batching events into the same execution, etc. While some of these are technically "not part of Lambda", to compete with Lambda CF needs the ecosystem as well.

Disclosure: 1. I'm an AMZN investor, therefore calling out that the ecosystem is worth keeping in mind. 2. I'm a NET investor, therefore calling out that I'm looking forward to seeing the ecosystem develop :)

I'd say that CloudFront Functions was a closer functional fit (and likely created in response to Cloudflare Workers). Lambda@Edge, despite the name, doesn't actually run at edge locations, but CloudFront Functions does.