Need advice about which tool to choose?Ask the StackShare community!
Engine Yard Cloud vs OpenShift: What are the differences?
Engine Yard Cloud: Deploy and scale Rails applications in the cloud. The Engine Yard Platform as a Service (PaaS) is a product family that leverages open source technologies to orchestrate and automate the configuration, deployment and management of applications on multiple infrastructures; OpenShift: Red Hat's free Platform as a Service (PaaS) for hosting Java, PHP, Ruby, Python, Node.js, and Perl apps. OpenShift is Red Hat's Cloud Computing Platform as a Service (PaaS) offering. OpenShift is an application platform in the cloud where application developers and teams can build, test, deploy, and run their applications.
Engine Yard Cloud and OpenShift can be categorized as "Platform as a Service" tools.
Some of the features offered by Engine Yard Cloud are:
- Dedicated, secure, commercial-grade platform that increases agility
- Focus on your code - not on operations or platform maintenance
- Scale cloud applications and infrastructure rapidly
On the other hand, OpenShift provides the following key features:
- Built-in support for Node.js, Ruby, Python, PHP, Perl, and Java (the standard in today's Enterprise)
- OpenShift is extensible with a customizable cartridge functionality that allows developers to add any other language they wish. We've seen everything from Clojure to Cobol running on OpenShift.
- OpenShift supports frameworks ranging from Spring, to Rails, to Play
"Great customer support" is the primary reason why developers consider Engine Yard Cloud over the competitors, whereas "Good free plan" was stated as the key factor in picking OpenShift.
OpenShift is an open source tool with 915 GitHub stars and 563 GitHub forks. Here's a link to OpenShift's open source repository on GitHub.
According to the StackShare community, OpenShift has a broader approval, being mentioned in 50 company stacks & 52 developers stacks; compared to Engine Yard Cloud, which is listed in 8 company stacks and 4 developer stacks.
Pros of Engine Yard Cloud
- Great customer support6
- Simple deployment1
Pros of Red Hat OpenShift
- Good free plan99
- Open Source63
- Easy setup47
- Nodejs support43
- Well documented42
- Custom domains32
- Mongodb support28
- Clean and simple architecture27
- PHP support25
- Customizable environments21
- Ability to run CRON jobs11
- Easier than Heroku for a WordPress blog9
- Easy deployment8
- PostgreSQL support7
- Autoscaling7
- Good balance between Heroku and AWS for flexibility7
- Free, Easy Setup, Lot of Gear or D.I.Y Gear5
- Shell access to gears4
- Great Support3
- High Security3
- Logging & Metrics3
- Cloud Agnostic2
- Runs Anywhere - AWS, GCP, Azure2
- No credit card needed2
- Because it is easy to manage2
- Secure2
- Meteor support2
- Overly complicated and over engineered in majority of e2
- Golang support2
- Its free and offer custom domain usage2
- Autoscaling at a good price point1
- Easy setup and great customer support1
- MultiCloud1
- Great free plan with excellent support1
- This is the only free one among the three as of today1
Sign up to add or upvote prosMake informed product decisions
Cons of Engine Yard Cloud
Cons of Red Hat OpenShift
- Decisions are made for you, limiting your options2
- License cost2
- Behind, sometimes severely, the upstreams1
Sign up to add or upvote consMake informed product decisions
What is Engine Yard Cloud?
What is Red Hat OpenShift?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Engine Yard Cloud?
What companies use Red Hat OpenShift?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Engine Yard Cloud?
What tools integrate with Red Hat OpenShift?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+14Rafay Systems
+8
+6