| Deno Deploy | Features | Amazon Lambda @ Edge |
|---|---|---|
| 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 compute pops |
| Default Memory (MB) | 128 | |
| Maximum Memory (MB) | 128 | |
| Execution Time (ms) | 5,000 | |
| Maximum Execution Time (ms) | 30,000 | |
| Request Payload (MB) | 50 | |
| Response Payload (MB) | .04 | |
| 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 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.
