Engine Yard vs. IBM Cloud Functions

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Engine Yard
Score 8.0 out of 10
N/A
Engine Yard is a platform-as-a-service solution allowing developers to plan, build, deploy, and manage applications in the cloud. Engine Yard also provides services for deployment, managing AWS, supporting databases, and microservices & container development.
$800
Per Month Per Cluster
IBM Cloud Functions
Score 7.0 out of 10
N/A
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
Pricing
Engine YardIBM Cloud Functions
Editions & Modules
Platform
$800.00
Per Month Per Cluster
Basic Cloud Functions Rate
$0.00017
per second of execution
API Gateway Rate
Free
Offerings
Pricing Offerings
Engine YardIBM Cloud Functions
Free Trial
YesNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Engine YardIBM Cloud Functions
Best Alternatives
Engine YardIBM Cloud Functions
Small Businesses
AWS Lambda
AWS Lambda
Score 8.3 out of 10
AWS Lambda
AWS Lambda
Score 8.3 out of 10
Medium-sized Companies
Red Hat OpenShift
Red Hat OpenShift
Score 9.2 out of 10
Red Hat OpenShift
Red Hat OpenShift
Score 9.2 out of 10
Enterprises
Red Hat OpenShift
Red Hat OpenShift
Score 9.2 out of 10
Red Hat OpenShift
Red Hat OpenShift
Score 9.2 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Engine YardIBM Cloud Functions
Likelihood to Recommend
8.0
(1 ratings)
3.0
(7 ratings)
Likelihood to Renew
8.0
(1 ratings)
-
(0 ratings)
User Testimonials
Engine YardIBM Cloud Functions
Likelihood to Recommend
Engine Yard
It is best for rapidly getting your application to the cloud without worrying about standing up cloud infrastructure
Read full review
IBM
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.
Read full review
Pros
Engine Yard
  • Quick deployments
  • Easily integrate your code from GitHub
  • Ability to recover site quickly to different zone when AWS has a widespread outage
Read full review
IBM
  • 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.
Read full review
Cons
Engine Yard
  • Embracing new Amazon Web Servicess(AWS) features
  • Security groups need more granularity
  • Audit trails of what happens by who in environment, especially when VM is deleted
Read full review
IBM
  • 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
Read full review
Likelihood to Renew
Engine Yard
Ease of use
Read full review
IBM
No answers on this topic
Alternatives Considered
Engine Yard
More closely aligns to native AWS
Read full review
IBM
  • 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
Read full review
Return on Investment
Engine Yard
  • Positive in the sense that we can deploy new applications quickly for MVP
Read full review
IBM
  • 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.
Read full review
ScreenShots