Amazon Lambda @ Edge compared to RedHat OpenShift

Amazon Lambda @ Edge
Versus
RedHat OpenShift

Features

Edge Features of Amazon Lambda @ Edge compared to RedHat OpenShift
Amazon Lambda @ EdgeFeaturesRedHat OpenShift
Functions / Serverless
javascript, go, C/++, .NET, Node.js, PHP, python, rubyFunctions supported languagesDockerized, so anything that runs inside a container.
Worker.js Environment
Yes, through EC2 Container Registry (ECR)Docker support
Docker private registry
Kubernetes support
Managed Kubernetes
All compute popsAvailability regionsWherever your own pops are
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 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.


RedHat OpenShift


If rolling your own is your style, then OpenShift is your platform to do it on.

100% open source, Red Hat’s OpenShift comes with a very big manual of course, but that’s what makes it complete and a true Red Hat product. First launched in 2011, OpenShift Container Platform’s has been a core component of OpenStack for years.

OpenShift packs a punch, but comes at the cost of having to maintain and own your hardware before you can really start.