fx VS OpenFaaS

Here’s a GitHub repo for an open-source serverless framework, if you want to experiment without full cloud lock-in.

As part of my research, I needed to evaluate the performance of Firecracker in serverless environments compared to traditional Linux containers. OpenFaaS, with its modular design, offered an excellent framework for this comparison. OpenFaas offered two running modes, which were OpenFaas using Kubernetes and faasd. Firecracker-containerd isn’t directly supported by Kubernetes due to the lack of a stable CRI plugin unless you consider the now unsupported Firekube. Extending faasd to support Firecracker is simpler and served as sufficient proof of concept from my research. Otherwise, from a general point of view, the primary advantage of Firecracker over LXC in serverless computing is isolation, which isn’t crucial if you’re running faasd since serverless loads on faasd are typically trusted. So, there is no big need to do this other than plain curiosity.

The FaaS platform gained a lot of popularity which resulted in many competitors. There was OSS providers like OpenFaaS or Fission. There were of course the commercial versions to like Azure Functions and Google Cloud Functions.

Serverless functions are now offered by many cloud providers, as well as having options like OpenFaaS, Knative, Apache's Openwhisk and more from the open source community that run in environments ranging from one server all the way up to globally replicated private clusters.

OpenFaaS

Did you consider running knative or openfaas? https://github.com/openfaas/faas

Anyone knows other alternatives for Azure Functions, but for DIY hosting? ( eg. OpenFaas - https://www.openfaas.com/ )

Maybe OpenFaaS with grafana and slack notifications for non-200 responses?