IBM Cloud Functions vs. Netlify Platform

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.

Netlify is a static website host, so it obviously wouldn't work for hosting dynamic websites built in PHP, such as WordPress or Drupal. It works very well with static sites with a git codebase on something like GitHub. It has automatic deployments, which include preview websites. It works very well with this workflow. There are solutions for allowing content authoring on static websites on Netlify, but I would probably reach for something like WordPress or Drupal for that.

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

• I can connect Github/Gitlab repos or drag and drop code folders directly to host them onto the platform, and can customize build and publish details. It handles all granular details itself, so I don't have to worry about configuring everything like I would have to do on an IaaS like AWS
• Netlify Platform has inbuilt scalability support - meaning automatic upgrading of servers to handle traffic, without us needing to do anything at all, again, unlike IaaS, where we'd have to manually configure scaling
• It has a built in CDN, meaning static applications can be served blazing fast over the web without worrying about traffic or latency

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

• it is not aimed at it but first party laravel support would be nice.
• their free tier was so handy, i wish they start some similar efforts
• incorporate more WebOps mindset

Incentivized

We interact with the CLI via our CI/CD pipeline. It was very straightforward to get set up, and their documentation is thorough. There are a ton of examples online of various setups. We needed to deploy a React SPA, so we required redirects, which was straightforward with Netlify.

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

Netlify Platform is the first choice that we are using in this organization continuously and it's been a very promising platform to use. It also maintains the things very well. it also giving a very good updates. It is very easy to use and very easy to learn. overall it is good.

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

• it's free to get started and to work on small frontend projects for testing and qa
• very nice DNS Management
• quick and easy to use, reduces dev efforts

Incentivized