21–30 of 65 posts
Comparing Workers to Lambda proper seems silly. Lambda lets you connect to DBs, use a lot more than 128MB of memory, etc, etc, etc. Comparing them to Lambda@Edge makes sense, but Lambda@Edge is not a very good product. (Full disclosure: my company competes with Cloud Flare Workers).
Have you think about including Golang based Lambda function in your benchmark? As you're guessing that Cloudfare superior JS runtime plays a big role, it could be interesting to see if it can compete against Golang Lambda as well.
On another note, currently we only support JavaScript, but we're putting the finishing touches on WebAssembly support, which would let you run Go on Workers... stay tuned.
What Infrastructure as Code (IaC) options exist for Cloudflare Workers? AFAICT neither Serverless nor Terraform support it. IaC is table stakes for any new part of my tech stack, and I would prefer not to code it from scratch - unless deployment/configuration is extremely easy to automate via CLI or something...
[1] - https://github.com/terraform-providers/terraform-provider-cl...
Not a very interesting benchmark. This would only measure net latency and spin-up time.
>To be fair, comparing my Lambda, which only runs in us-east-1 (Northern Virginia, USA), to a global service like Workers is a a little unfair. At least you acknowledge that it's a bit silly to use a global benchmark to compare a global service with an intentionally-regionalized service.
Why would you run something in a single location if you can run it everywhere for the same price though? It's not like Lambda is cheaper for being centralized.
For the specific use case you tested workers on the edge absolutely make more sense than lambda, but I think the headline is a bit click-baity.
> The functions being tested simply return the current time Not a very interesting benchmark. This would only measure net latency and spin-up time.