| Akamai Edge Workers | Features | Amazon Cloudfront Functions |
|---|---|---|
| Functions / Serverless | ||
| JavaScript, possibly Python (1 example with Python code in their repo) | Functions supported languages | JavaScript, Go, C/++, .NET, Node.js, PHP, Python, Ruby |
| Worker.js Environment | ||
| No | Docker support | Yes, through EC2 Container Registry (ECR) |
| Docker private registry | ||
| Kubernetes support | ||
| Managed Kubernetes | ||
| Over 4100 POPs worldwide | Availability regions | All POPs connected to your Cloudfront property |
| Default Memory (MB) | 128 | |
| Maximum Memory (MB) | 3008 | |
| Execution Time (ms) | 3,000 | |
| Maximum Execution Time (ms) | 900,000 | |
| Request Payload (MB) | 6 | |
| Response Payload (MB) | 6 | |
| Unsupported Paid Feature Supported Unknown | ||
Amazon Cloudfront Function introduces cloud computing to every CloudFront pop around the globe.
Amazon Cloudfront Functions differs from Amazon’s [email protected] 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 [email protected] in the long term?
