Amazon Lambda @ Edge compared to Cloudflare Workers

Amazon Lambda @ Edge
Versus
Cloudflare Workers

Features

Edge Features of Amazon Lambda @ Edge compared to Cloudflare Workers
Amazon Lambda @ EdgeFeaturesCloudflare Workers
Functions / Serverless
javascript, go, C/++, .NET, Node.js, PHP, python, rubyFunctions supported languagesjavascript, rust, C/++
Worker.js Environment
Yes, through EC2 Container Registry (ECR)Docker support
Docker private registry
Kubernetes support
Managed Kubernetes
All compute popsAvailability regions200 pops
128Default Memory (MB)128
128Maximum Memory (MB)128
5,000Execution Time (ms)10
30,000Maximum Execution Time (ms)50
50Request Payload (MB)
.04Response Payload (MB)
Unsupported Paid Feature Supported Unknown

Descriptions


Amazon Lambda @ Edge


Amazon Lambda at the Edge functions introduced serverless cloud computing to the masses as early as 2014.

Being the first with a massive user-base has set up Amazon for great success, it took a few years for competitors to offer similar functionality and to actually call the FaaS space a new chapter in cloud compute in general.

Amazon’s [email protected] is Amazon’s first Edge Compute product, however Amazon recently released CloudFront Functions, which brings the compute a lot closer to the end-user.

With Amazon’s gigantic scale, a shift has started with companies that are on the AWS platform to move more and more of their infrastructure to serverless.


Cloudflare Workers


Continuing their ongoing efforts to improve the internets global state, Cloudflare started to allow compute at their edge, eventually and essentially becoming a serverless/edge compute provider.

Cloudflare has an impressive global network presence and an even more impressive rate of pushing (open source or free) products to the market.

Unique about Workers is Key Value storage. Cloudflare’s low latency KV data store, optimized for high reads, low writes.

With a rich amount of example code to start out in your code of preference right away!