count VS terraform-provider-openfaas

I probably should add a terraform based approach to deploying my "count" HTTP API here: https://github.com/kaihendry/count

https://github.com/kaihendry/count/blob/sam/template.yml

All in one file.

Alex, OpenFaaS founder here. The author has done a huge amount of work here, I am surprised that it's being given away for free, and not being monetized (it should be).

I often hear folks complain that Kubernetes is complex, and hard to understand. We've done a lot of work to make the experience of deploying functions simple on K8s, with very little to manage. But it still costs you a K8s cluster.

We created a new of openfaas called "faasd" which can run very well somewhere like DO or Hetzner for 3 EUR / mo. It doesn't include clustering, but is likely to be suitable for a lot of folks, who don't want to get deep into IAM territory.

The REST API for OpenFaaS has a terraform provider that works with either version - https://github.com/ewilde/terraform-provider-openfaas

And there's a guide on setting up faasd with TLS on DigitalOcean, it took about 30 seconds to launch, and makes building functions much simpler than Lambda. "faas-cli up"

https://www.openfaas.com/blog/faasd-tls-terraform/

If I were going to use Lambda, the author's examples are probably what I would turn to, but there are other ways and it needn't be this complex.