Basic OpenFaaS repo stats
1 day ago

openfaas/faas is an open source project licensed under MIT License which is an OSI approved license.

OpenFaaS Alternatives

Similar projects and alternatives to OpenFaaS based on common topics and language

  • GitHub repo Previous Serverless Version 0.5.x

    ⚡ Serverless Framework – Build web, mobile and IoT applications with serverless architectures using AWS Lambda, Azure Functions, Google CloudFunctions & more! –

  • GitHub repo crossplane

    Manage any infrastructure your applications need directly from Kubernetes

  • GitHub repo kubefed

    Kubernetes Cluster Federation

  • GitHub repo faasd

    A lightweight & portable faas engine

  • GitHub repo spec

    Container Storage Interface (CSI) Specification. (by container-storage-interface)

  • GitHub repo openfaas-puppeteer-template

    OpenFaaS template for headless Chrome and Puppeteer

  • GitHub repo fx

    A Function as a Service tool makes a function as a container-based service in seconds. (by metrue)

NOTE: The number of mentions on this list indicates mentions on common posts. Hence, a higher number means a better OpenFaaS alternative or higher similarity.


Posts where OpenFaaS has been mentioned. We have used some of these posts to build our list of alternatives and similar projects - the last one was on 2021-04-20.
  • Why we moved from Lambda to ECS | 2021-04-20
    OpenFaaS isn't something I was previous familiar with. Thanks for linking it! In your experience, does it come with much management overhead? Part of what makes Lambda/ECS so appealing is that you can throw a definition (code .zip file or container image) at AWS, and it just runs. With OpenFaaS, it looks like you need to maintain some additional infrastructure (a Kubernetes cluster) to get it working, and that'd give you one more thing to worry about.
  • Infrastructure Engineering — Deployment Strategies | 2021-02-13
    Serverless: Serverless has long been seen as the final step to elastic computing. And while it seems ambitious, it cannot completely replace containers, virtual machines or bare metal deployments. It is to be seen as a great complement to them all considering the significant limitations they have. When you want to go for serverless you have to take into account a few things like Cold/Warm/Hot start of serverless functions since that decides the latency of the response you are going to get, keep in mind that every cloud provider has a timeout for execution like 15 minutes in case of AWS, 9 minutes in case of Google Cloud functions, 10 minutes for Azure Functions and so on making it unsuitable for long running jobs. In addition to this, there are also restrictions to the programming languages you can use in your serverless function (unless you are opting in for a container based deployment which essentially makes it a container based deployment 🤔) . If you still want to use serverless for long running jobs, you might have to reach out to them for dedicated/premium plans or maintain your own serverless infrastructure within your Kubernetes cluster using something like KNative, OpenFaas, Kubeless or similar and setting your own limits.
  • Show HN: OpenFaaS template for headless Chrome and Puppeteer | 2021-01-05
    Did you try the docs, the blog or YouTube? You'll find plenty of information there. Feel free to start with