| RedHat OpenShift | Features | Fly.io |
|---|---|---|
| Functions / Serverless | ||
| Dockerized, so anything that runs inside a container. | Functions supported languages | |
| Worker.js Environment | ||
| Docker support | ||
| Docker private registry | ||
| Kubernetes support | ||
| Managed Kubernetes | ||
| Wherever your own pops are | Availability regions | |
| Default Memory (MB) | ||
| Maximum Memory (MB) | ||
| Execution Time (ms) | No limit | |
| Maximum Execution Time (ms) | No limit | |
| Request Payload (MB) | No limit | |
| Response Payload (MB) | No limit | |
| 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.
Fly is an opensource runtime for edge apps, Fly offers a paid hosted version of their product as well. This provider will focus on the paid hosted version. Fly.io is one of the few companies and products that has a full range of tools alongside their actual product, which makes them an ideal candidate for curious developers and new companies to experiment.
Everything they do is docker based, and their networking abstraction is top notch, it’s clear Fly will play a major role in turning the space into a more user-friendly one. Fly’s ambitious mission to make application distribution as ubiquitous as CDNs sets the bar for any contenter willing to compete.
