IBM Cloud Functions vs. Superblocks

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.

Superblocks is great for building internal tools for your company. We have our finances running on Superblocks, our client services running on it, as well as a lot of internal tooling for our product. You can build full-apps using their API builder, Workflow builder, Scheduled Jobs, and UI builder. All without having to handle your own infrastructure. It's meant to be one extra abstraction layer on top of other developer infrastructure tools like AWS, Vercel, etc.

• 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

• Easy to use User Interface builder for building internal apps
• Scheduled Jobs and Workflow builder in multiple languages
• API builder for support your User Interface for your internal apps

• 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

• More flexibility on UI component designs

• 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

• 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

• We've saved thousands of developer hours that would have otherwise spent on maintaining infrastructure