Google Cloud Functions vs. IBM Cloud Functions

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

IBM Cloud Functions [is] not the worse product on the IBM cloud. I decided to write this review as I thought it would be balanced. I would still use functions to set up a serverless architecture where execution time is pretty quick and the code is relatively simple. I wouldn't use IBM Cloud Functions for async calls obviously, as costs could be higher. The functions documentation is lacking in terms of CI/CD, and there are unexplainable errors occurring - like the network connection that I mentioned. So I wouldn't just rely on IBM Cloud Functions too much for the entire system, but make sure it's diversified.

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

Incentivized

• Great substitute for a simple API calls to run non-complicated code.
• Easy way to run Python/Java/Javascript to get something done.
• File validation.

Incentivized

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

Incentivized

• Billing can be a hassle, not the most responsive customer service/support team
• Handles & executes most functionalities, but other platforms offer more scalability if you're seeking consistent and stable growth

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

• ICF is a lightweight service and does not require runtime configurations
• Scalable on demand and hence there is no need to pay for runtime costs

Incentivized

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

Incentivized

• It directly affected our expenses since we do not need to deploy and maintain a set of separate applications.
• It allowed us to pay for only the amount of time cloud functions run.
• It saved on maintenance and monitoring of the applications it replaced.

Incentivized