Recommended reads

Run Cloudflare Worker Locally with Docker
Tutorial
December 5, 2022
4 mins

Run Cloudflare Worker Locally with Docker

Read article
Splitbee acquired by Vercel - A threat for Fastly?
November 10, 2022
1 min

Splitbee acquired by Vercel - A threat for Fastly?

Read article
What is cloudgaming and why will it be big 5 years from now
August 13, 2022
9 mins

What is cloudgaming and why will it be big 5 years from now

Read article
Find Out What's Next For Deno After Raising $21M
July 14, 2022
4 mins

Find Out What's Next For Deno After Raising $21M

Read article
The Difference between Serverless and Edge Compute
June 1, 2022
2 mins

The Difference between Serverless and Edge Compute

Read article

Amazon Cloudfront Functions compared to Amazon Lambda @ Edge

Amazon Cloudfront Functions
Versus
Amazon Lambda @ Edge

Features

Edge Features of Amazon Cloudfront Functions compared to Amazon Lambda @ Edge
Amazon Cloudfront FunctionsFeaturesAmazon Lambda @ Edge
Functions / Serverless
JavaScript, Go, C/++, .NET, Node.js, PHP, Python, RubyFunctions supported languagesjavascript, go, C/++, .NET, Node.js, PHP, python, ruby
Worker.js Environment
Yes, through EC2 Container Registry (ECR)Docker supportYes, through EC2 Container Registry (ECR)
Docker private registry
Kubernetes support
Managed Kubernetes
All POPs connected to your Cloudfront propertyAvailability regionsAll compute pops
128Default Memory (MB)128
3008Maximum Memory (MB)128
3,000Execution Time (ms)5,000
900,000Maximum Execution Time (ms)30,000
6Request Payload (MB)50
6Response Payload (MB).04
Unsupported Paid Feature Supported Unknown

Descriptions

Amazon Cloudfront Functions

Amazon Cloudfront Function introduces cloud computing to every CloudFront pop around the globe.

Amazon Cloudfront Functions differs from Amazon’s Lambda@Edge because CloudFront’s servers have been located traditionally at the edges of Amazon’s gigantic global network of servers. This means CloudFront functions will run closer to the end-user than traditional Lambda’s, which usually run within customers' own VPN or behind loadbalancers.

With this change in approach, Amazon hopes to even further play into the serverless space that is to become the future of IaaS or Serverless as a Service.

Given Amazon’s massive reach and the tremendously popular CloudFront product, this will surely be a success going forward. Perhaps even replacing Amazon’s Lambda@Edge in the long term?

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 Lambda@Edge 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.

Comparisons