Amazon Lambda @ Edge compared to Stackpath Serverless

Amazon Lambda @ Edge
Versus
Stackpath Serverless

Features

Edge Features of Amazon Lambda @ Edge compared to Stackpath Serverless
Amazon Lambda @ EdgeFeaturesStackpath Serverless
Functions / Serverless
javascript, go, C/++, .NET, Node.js, PHP, python, rubyFunctions supported languagesC/++, Go, Javascript, PHP, Perl, Python, Rust
Worker.js Environment
Yes, through EC2 Container Registry (ECR)Docker support
Docker private registry
Kubernetes support
Managed Kubernetes
All compute popsAvailability regions45 pops globally
128Default Memory (MB)
128Maximum Memory (MB)
5,000Execution Time (ms)
30,000Maximum Execution Time (ms)
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.


Stackpath Serverless


Stackpath’s dominant reign in the CDN space allowed space to expand their activity to the FaaS space.

Stackpath’s Sanbox environment to test functions works very fast and requires no registration, domain name or anything for that matter.

Having acquired at least 5 sizable companies in the last few years, it was only a waiting game before they announced to run serverless on their backbone-powered super fast infrastructure.

Having their own Backbone, Stackpath will be able to deliver on their promise to deliver at the microsecond.