Cloud Foundry vs OpenShift: What are the differences?
Developers describe Cloud Foundry as "Deploy and scale applications in seconds on your choice of private or public cloud". Cloud Foundry is an open platform as a service (PaaS) that provides a choice of clouds, developer frameworks, and application services. Cloud Foundry makes it faster and easier to build, test, deploy, and scale applications. On the other hand, OpenShift is detailed as "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.
Cloud Foundry and OpenShift can be categorized as "Platform as a Service" tools.
Some of the features offered by Cloud Foundry are:
- Application and services centric lifecycle API
- High performance dynamic routing
- Buildpack support
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
Cloud Foundry and OpenShift are both open source tools. It seems that OpenShift with 915 GitHub stars and 563 forks on GitHub has more adoption than Cloud Foundry with 605 GitHub stars and 532 GitHub forks.
According to the StackShare community, OpenShift has a broader approval, being mentioned in 50 company stacks & 52 developers stacks; compared to Cloud Foundry, which is listed in 8 company stacks and 13 developer stacks.
What is Cloud Foundry?
What is Red Hat OpenShift?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Cloud Foundry?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Heroku vs OpenShift. I've never decided which one is better. Heroku is easier to configure. Openshift provide a better machine for free. Heroku has many addons for free. I've chosen Heroku because of easy initial set-up. I had deployment based on git push. I also tried direct deployment of jar file. Currently Heroku runs my Docker image. Heroku has very good documentation like for beginners. So if you want to start with something, let's follow Heroku. On the other hand OpenShift seems like a PRO tool supported by @RedHat.
I needed a PaaS provider that didn't drop all the time and it's hard to find a good option for PHP applications. Openshift takes care of it. They are a little behind on PHP versions, but that can be solved with a custom cartridge. It requires a little more elbow grease to get rolling when you want to implement something they don't already have, but their quickstarts are great to get rolling with the basics quickly.
SG-TravelBuddy server application is hosted on Red Hat OpenShift Online (v3). SG-TravelBuddy mobile (Android) app is connecting to this server for data operations.
Easy host and monitor the application on the cloud, using a platform that is hight integrated with Spring Framework, but is also agnostic of technology