| RedHat OpenShift | Features | Stackpath Serverless |
|---|---|---|
| Functions / Serverless | ||
| Dockerized, so anything that runs inside a container. | Functions supported languages | C/++, Go, Javascript, PHP, Perl, Python, Rust |
| Worker.js Environment | ||
| Docker support | ||
| Docker private registry | ||
| Kubernetes support | ||
| Managed Kubernetes | ||
| Wherever your own pops are | Availability regions | 45 pops globally |
| Default Memory (MB) | ||
| Maximum Memory (MB) | ||
| Execution Time (ms) | ||
| Maximum Execution Time (ms) | ||
| Request Payload (MB) | ||
| Response Payload (MB) | ||
| 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.
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.
