Red Hat OpenShift vs Pivotal Web Services (PWS): What are the differences?
Red Hat 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; Pivotal Web Services (PWS): Deploy, Update and Scale Applications On-Demand. Pivotal Web Services is a public cloud version of the widely supported Open Source Cloud Foundry PaaS. PWS makes is an ideal platform for the rapid deployment, easy scaling and binding of third party apps for Java, PHP, Ruby, GO and Python apps. Focus on apps not dev ops.
Red Hat OpenShift and Pivotal Web Services (PWS) can be primarily classified as "Platform as a Service" tools.
Some of the features offered by Red Hat OpenShift are:
- 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
On the other hand, Pivotal Web Services (PWS) provides the following key features:
- Marketplace for 3rd party services
- Cloud Foundry Support
- Easy Deployment
Red Hat OpenShift is an open source tool with 911 GitHub stars and 562 GitHub forks. Here's a link to Red Hat OpenShift's open source repository on GitHub.
What is Pivotal Web Services (PWS)?
What is Red Hat OpenShift?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Pivotal Web Services (PWS)?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Pivotal Web Services (PWS)?
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.