| Deno Deploy | Features | Amazon Cloudfront Functions |
|---|---|---|
| Functions / Serverless | ||
| Typescript, javascript/ES, WASM | Functions supported languages | JavaScript, Go, C/++, .NET, Node.js, PHP, Python, Ruby |
| Worker.js Environment | ||
| Docker support | Yes, through EC2 Container Registry (ECR) | |
| Docker private registry | ||
| Kubernetes support | ||
| Managed Kubernetes | ||
| 28 pops around the globe | 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 | ||
Deno is a new open source rust-based typescript v8 javascript engine.
Deno recently launched their Deno Deploy product, which is a full fledged edge compute platform completely built for the Deno/javascript/typescript landscape.
Deno offers a nice local worker environment which full support for Worker Environments.
The Deno library size is not that big at the time of writing, but with the underlying tech, this should only be a matter of time.
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?
