Google Cloud Functions vs. OpenFaaS

Any sort of transaction or complex logic that is going to take longer than 250ms or accesses resources that are protected by permissions, secrets, etc. is a great use case for a GCF. Some sort of "helper function" associated strictly with the UI inside browser would not be a good application of a GCF. It would not be crazy to create/debug some fairly complicated logic inside the browser/IDE and when perfected package it up as a Google Cloud Function. I have done that many times.

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

The console UI is pretty nasty. Managing various authentication/permissions configurations is just a nightmare. On the other hand, once you are over the hump it's not so bad. AWS Lambda is no better.

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