| RedHat OpenShift | Features | Amazon Cloudfront Functions |
|---|---|---|
| Functions / Serverless | ||
| Dockerized, so anything that runs inside a container. | 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 | ||
| Wherever your own pops are | 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 | ||
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.
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?
