Google Cloud Functions vs. OpenFaaS

It is easy to use, in 15 minutes you just have to follow a few steps, do some easy configurations and you have the project ready to run, once it is connected to the codebase, the execution is automatic. For anyone coming into the google environment, Functions make code execution easy and transparent. CI/CD is perfect

Incentivized

• integration with oAuth
• integration with Firebase
• integration with React Frontend

Incentivized

• Needing a zip file is problematic (when wanting to automate deployment for example).
• Requires another solution to execute automatically (ex. cloud scheduler).

Incentivized

Overall Google Cloud Functions is losing a lot of benefits to other GCP services, making it less attractive to users. A simple example would be the need to zip application files and push them to Google Storage which makes it a bit complicated to automate via a CI/CD pipeline. Another "similar" solution would be using Cloud Run although the need for a docker image is there, with the recent evolutions to Cloud Run (ability to downscale to 0) it makes a lot more interesting.

Incentivized

Documentation is provided and clear for this service. Although GCP support is included in the current contract we didn't get to use it since the process is pretty straightforward.

Incentivized

It is easier to keep everything in house when we are using GCP or AWS. To mix Lambda with google cloud is not a best practice and will cause problems ahead. The segmentation is clear, if you are using google, you use Google Cloud Functions. if you are on Amazon, you use all AWS tools. You can't mix them. The price is set.

Incentivized

• For training purposes, it is free
• Budgeting makes it cap the use
• monitoring makes it predictable

Incentivized