faasd VS functions-framework

If you don't want to start with Kubernetes, faasd (https://github.com/openfaas/faasd) might be worth a look.

I found OpenFaaS and its little sibling faasd. To my understanding they expose single functions through a REST API for easy interfacing. It sounds nice but OpenFaaS is overkill and I had trouble setting up faasd.

Hope you find this interesting / useful - whether you're using AWS Lambda, OpenFaaS, or just plain old Go binaries. If you're wondering whether OpenFaaS requires K8s, you also have faasd as an option.

Have you seen faasd from openfaas? Easier to setup and doesn‘t require a full blown kubernetes cluster: https://github.com/openfaas/faasd

I'm the original creator of faasd, and just found this post on the Internet. What I liked was how he discovered faasd and found some unique value in it.

I wanted to share it all with a broader audience here. His bootstrap is a little bit convoluted, if you check out GitHub, we have a simple installer script and an eBook as a reference manual.

https://github.com/openfaas/faasd

First of all, you need faas-cli in your client local machine. You should get the binary and set it to your path. If you are on linux or mac machine, moving the binary into "/usr/local/bin" will work. For windows machines, you need to set environment variables in Control Panel>System and Security>System>Advanced System Settings(single-binary-faas-cli)

Have you considered OpenFaaS - https://github.com/openfaas/faasd

I am on the same ship, after some digging around I'm considering OpenFaaS, checkout - https://github.com/openfaas/faasd

If you use https://github.com/openfaas/faasd, you can skip the whole Kubernetes setup as well.

So, you want to run multiple node.js Google Cloud Functions locally at the same time using Google’s functions-framework?

Functions Framework: Both Google Cloud Functions and Cloud Functions for Firebase users can opt to use the Google Cloud open source project known as the Functions Framework to run their functions locally, on their own servers, or deployed to the cloud if desired. The first pair of options are low/no-cost other than what you pay for your servers.

* Speaking of which, a FunctionsFramework library gives us a place to put the unit testing library, tools to spin up a functions server locally for testing, and whatever tools developers might find useful in the future.

For reasons such as these, Google's overall Cloud Functions team decided to produce framework libraries for all supported languages. There's a contract and everything that our Ruby gem follows. (https://github.com/GoogleCloudPlatform/functions-framework)