IBM Cloud Functions is a PaaS platform based on Apache OpenWhisk. With it, developers write code (“actions”) that respond to external events. Actions are hosted, executed, and scaled on demand based on the number of events coming in. No servers or infrastructure to provision and manage.
$0
per second of execution
Quali CloudShell
Score 9.1 out of 10
N/A
CloudShell, from Quali headquartered in Austin, is an infrastructure automation solution for cloud, on-premise, or hybrid environments.
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.
Validate raw data files - check the validity of raw data input to the system, to make sure we analyze only the relevant data. The raw data stream rate is hard to be predicted, since it depends on real world activities.
Analyze raw data - analyzing of valid raw data, described above.
The tool can automate almost any workflow and infrastructure consumption. It has state of the art develop and support with great online training, online full manual set, and a comprehensive support team and network of SIs/VARS that are very qualified.
AWS Lambda is 100 times more robust than IBM cloud functions. They essentially do the same thing, but AWS works. AWS is stable. we have had epic failures with cloud functions. Support was horrible. We literally had an open ticket with them for 2 months and it literally went nowhere. They said it could do 100 calls a minute. We proved over and over that we couldn't get above 20 without getting failures. They had NO explanation whatsoever. The ticket got closed because we were tired of asking them questions and getting no understandable or usable response.
VMware is too hard to use, too expensive to support, and not a full lifecycle tool for workflows and Infrastructure (no support of physical either). AWS or Azure or Google solutions are good if you are only in the cloud and only using their tools. Not good if you have on-prem or non-Cloud based tools/infrastructure. Build it yourself automation frameworks can be good for people with unlimited funds, but they are not the best way to go and missing many capabilities typically.