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
Rackspace Fabric
Score 6.3 out of 10
N/A
A solution to bring cloud security, billing, operations and management together. Rackspace Fabric offers a single platform for automated multicloud management. Service includes access to Rackspace cloud technology expertise, and provides a unified interface management for all cloud resources across Azure, AWS, GCP, and VMware, in a single, SaaS like operating environment.
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.
I am highly likely to recommend Rackspace Cloud Monitoring to a colleague. This is assuming they have a decent background in working on cloud servers. If you don't mind digging in yourself to solve problems, then this is a great resource. If you are just learning how to set up servers on your own, then I recommend at least hiring someone to help you use the service. With that being said, Rackspace makes it easy for people you may hire to seamlessly work within your account. They get their own separate developer account.
Immediate email notifications: In case a service is down on our servers, we get immediate email notifications via rackspace cloud monitoring service. This helps us to know about the issues and we get in contact with support team to get it resolved.
Configuration on specific services: We can configure this monitoring on specific services. So for example if i don't want to get notified if MySQL concurrent users limit reached, then I do not need to configure this monitoring for MySQL. I can just use it whenever needed for defined services.
Group emails and technical contacts emails: The monitoring service can send email alerts to a number of email addresses. Primarily the ones who are added as a technical contact. It helps all people get notified about any issue.
Auto ticket management: Rackspace automatically creates a support ticket when a service is down and is notified by their monitoring service.
I also used Monitis as a monitoring service for our server. Rackspace'S monitoring sends immediate notifications while Monitis might take a couple minutes to understand if a service is down. Since Rackspace has their monitoring integrated with their support system, it helps us a lot and we don't need to call support all the time.
