faasd VS serverless-graphql

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.

Since then, the ecosystem has changed. Using the Serverless Framework makes deployment simpler. We released the managed Tracetest App making any serverless-based systems simpler to instrument and test. You can now test public-facing apps with no infra overhead!

We see some great results from using these in conjunction with frameworks such as SST or Serverless, and also some real spaghetti from people who organically proliferate 100’s of functions over time and lose track of how they relate to each other or how to update them safely across time and service. Buyer beware!

When we think about AWS serverless service, the first thing that comes to our mind is Lambda function. Yes, the quickest way to deploy this backend Express JS app to AWS is to deploy it as a Lambda function. The easiest way is using Serverless Framework.

Serverless Framework: https://www.serverless.com/

Github | Website

In this example, we're using the serverless framework to quickly set up the Lambda function along with an API gateway for the entry point. The lambda function is a simple Koa REST API with a few functional endpoints.

Naturally, there are several options available to declare your cloud resources. The options with the most popularity are the CDK, AWS CloudFormation, SST, Serverless framework, Terraform, and AWS SAM. There are others, but when talking about Infrastructure as Code (IaC), these are the ones you hear about most often.

1 - Serverless + AWS CDK + Lift: An integration that amps up the traditional Serverless Framework with Lift's static frontend construct and CDK's robust infra definition.

It's a bit easier in Python if you use tools like https://www.serverless.com/. I'm not sure if Rust has something similar yet.

Serverless