Not the worse IBM product
Our IBM Cloud Functions [connects] various services by picking up JSON data from buckets at a certain time interval, modifying it, and …
IBM Cloud Functions
IBM Cloud Functions
Starting at $0 per second of execution
View PricingOverview
Recent Reviews
Popular Features
View all 1 featuresScalability (7)
4.0
40%
Video Reviews
Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of IBM Cloud Functions, and make your voice heard!
Pricing
View all pricingBasic Cloud Functions Rate
$0.00017
Cloud
per second of execution
API Gateway Rate
Free
Cloud
Entry-level set up fee?
- No setup fee
For the latest information on pricing, visithttps://console.bluemix.net/openwhisk/l…
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting / Integration Services
Features Scorecard
Platform-as-a-Service
4.0
40%
Product Details
What is IBM Cloud Functions?
IBM Cloud Functions is a serverless programming platform based on Apache OpenWhisk. Developers use their favorite programming language to write code (“actions”) that responds to external events. Actions are hosted and executed in IBM Cloud, and scale on demand based on the number of events coming in. There are no servers or other infrastructure to provision and manage.
Actions respond to a variety of events. Typical events include periodic timers for batch job processing, HTTP-based API requests for implementing RESTful APIs using Functions, and responding to change events requests from IBM Cloud services like Cloudant and IBM Cloud Event Streams, and third-party events like Slack and GitHub state changes.
Because Cloud Functions is a serverless, event-driven platform, you don't need to explicitly provision servers. Developers working with chatbots, blockchain, AI, APIs, microservices, mobile, IoT, and many other apps can focus on writing app logic instead of worrying about auto-scaling, high availability, updates, and maintenance. Out of the box auto-scaling and load balancing means that you don't have to manually configure clusters, http plugins, and so on. IBM takes care of all of the hardware, networking, and software administration. All you have to do is provide the code.
IBM Cloud Functions Features
Platform-as-a-Service Features
- Supported: Scalability
Additional Features
- Supported: Elastic load balancing
- Supported: Template library of pre-written functions encapsulating common use cases
- Supported: Runtime build pack support for NodeJS, Python 2.7, Python 3, Swift, Ruby, Java, and executable programs written in Go, C++, shell script, etc.
- Supported: “Bring Your Own Container” runtime support – users can provide a docker container image for their function action(s).
IBM Cloud Functions Integrations
- GitHub
- Any 3rd party service where they support a webhook/trigger API (e.g. slack
- twilio)
IBM Cloud Functions Competitors
- AWS Lambda
- Azure functions
- Google functions
IBM Cloud Functions Technical Details
| Deployment Types | SaaS |
|---|---|
| Operating Systems | Unspecified |
| Mobile Application | No |
| Supported Countries | United States, United Kingdom, Australia, Germany |
| Supported Languages | English, French, German, Italian, Japanese, Korean, Portugese/Brazil, Spanish, Chinese simplified & traditional |
Frequently Asked Questions
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.
AWS Lambda are common alternatives for IBM Cloud Functions.
Reviewers rate Scalability highest, with a score of 4.
The most common users of IBM Cloud Functions are from Enterprises (1,001+ employees) and the Information Technology & Services industry.
Comparisons
View all alternatives
Reviews and Ratings
(54)
Reviews
(1-7 of 7)- Popular Filters
Companies can't remove reviews or game the system. Here's why
June 01, 2021
Not the worse IBM product
Our IBM Cloud Functions [connects] various services by picking up JSON data from buckets at a certain time interval, modifying it, and saving it to another bucket. We also have functions that connect to NLU, functions that connect to API endpoints, etc.
- Relatively updated in terms of node versions supported
- A trigger just stopped working for no reason at all. The IBM support team classified the issue as "Network connection dropped", we had huge costs associated with the outage.
- There is no CI/CD setup through the dashboard, Toolchain doesn't work with functions, so we had to implement a manual solution.
- The function code execution time is too slow - we tested the execution time of a function and a code running in a Cloud Foundry app and came up with 600ms for the function and 300ms for the CF app.
- Documentation in terms of CI/CD is also a little bit hard to get, not enough examples of manifest files that include triggers, functions, and API endpoints.
We have several python functions that we had set up as API calls, but we have changed them to be cloud functions instead. We are using these on different applications for several different clients. These perform operations such as validating files, computing a value based off of a previously set up machine learning model and more complex report/database queries that take more than a second or two.
- 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.
- They are not good if you are doing repetitive calls multiple times a minute.
- They are not good for long processes.
- They are not 100% reliable yet, they have been release for GA, but they don't standup to being beat up.
July 02, 2019
IBM Cloud Functions user
We use IBM Cloud Functions in multiple client-facing projects. It allows us to quickly perform small tasks and checks without starting up complex infrastructure.
- Quick setup
- Able to handle multiple languages
- Easy to scale
- Limit on the max number of concurrent calls
- Instability of the platform
- Limit on the total size of the deployment
June 05, 2019
Serverless computing
We use it to compute the identity of the type of file being uploaded and also do a bunch of computing when required. Also, we use it for daily jobs.
- Scalable
- Easily triggered when needed.
- Log auditing is easy with all the filtering.
- Saves on the hassle of maintaining apps.
- Needs to be consistent, had issues for a few days when it didn't work as expected.
February 20, 2019
Serverless computing is future and IBM Cloud Functions is here
We are using IBM Cloud Functions (ICF) to create enterprise level platforms that work with IBM Watson Cognitive services to do event-based processing. We have developed a platform to create Watson Assistant based virtual agents which use IBM Cloud Functions to fetch data from back-end systems or DB.
- ICF is a cost-effective solution when it comes to a cloud-based solution. We used Spring Boot Micro-services previously but it was costly because the application is continuously running and hence incurs operating costs even if the services are not used by the application.
- It scales very well and without too many manual interventions from the developers or support team. This is very useful when we have applications catering to large user bases like a chatbot or payment wallet.
- The ICF also works well in high demand data processing based on events (i.e. in a virtual agent platform) Whenever we receive a new chat request, the ICF can trigger sentiment analysis to analyze the chats.
- Need more out of the box support and integration to receive events from services like MongoDB and NoSQL databases.
February 14, 2019
Good Functions for a Good Price
We use IBM Cloud Functions on a case by case basis for our app development teams. It helps our teams and developers scale on mobile and easily with swift integration
- Makes mobile scalability really user-friendly, easy language integration
- Good for triggering IoT apps when certain criteria/validations are met
- 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
December 17, 2018
Serverless or server based? A short opinion
IBM Clound Functions are used to validate and analyze raw data that its arrival time and size hard to be predicted, since it depends on real world activities.
- 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.
- Insert data to LOCAL data base.
- APIs - cloud functions are charged based on usage time and needed computing power, when response time is something you can't enforce, like when using 3rd party APIs, you might pay for just waiting for reply.
- Services - when using function for services, make sure it is really needed ... sometimes a legacy VM service will do the best job.
- Programming languages - not all languages are supported (but you can run binary files if needed).