Heroku vs OpenShift vs Pivotal Web Services (PWS)

Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Heroku
Heroku

8.1K
5.7K
+ 1
3.1K
OpenShift
OpenShift

527
482
+ 1
467
Pivotal Web Services (PWS)
Pivotal Web Services (PWS)

21
27
+ 1
0
- No public GitHub repository available -
- No public GitHub repository available -

What is Heroku?

Heroku is a cloud application platform – a new way of building and deploying web apps. Heroku lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling.

What is OpenShift?

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.

What is Pivotal Web Services (PWS)?

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.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Heroku?
Why do developers choose OpenShift?
Why do developers choose Pivotal Web Services (PWS)?
    Be the first to leave a pro

    Sign up to add, upvote and see more prosMake informed product decisions

      Be the first to leave a con
      Jobs that mention Heroku, OpenShift, and Pivotal Web Services (PWS) as a desired skillset
      What companies use Heroku?
      What companies use OpenShift?
      What companies use Pivotal Web Services (PWS)?

      Sign up to get full access to all the companiesMake informed product decisions

      What tools integrate with Heroku?
      What tools integrate with OpenShift?
      What tools integrate with Pivotal Web Services (PWS)?

      Sign up to get full access to all the tool integrationsMake informed product decisions

      What are some alternatives to Heroku, OpenShift, and Pivotal Web Services (PWS)?
      DigitalOcean
      We take the complexities out of cloud hosting by offering blazing fast, on-demand SSD cloud servers, straightforward pricing, a simple API, and an easy-to-use control panel.
      Google App Engine
      Google has a reputation for highly reliable, high performance infrastructure. With App Engine you can take advantage of the 10 years of knowledge Google has in running massively scalable, performance driven systems. App Engine applications are easy to build, easy to maintain, and easy to scale as your traffic and data storage needs grow.
      Firebase
      Firebase is a cloud service designed to power real-time, collaborative applications. Simply add the Firebase library to your application to gain access to a shared data structure; any changes you make to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds.
      Docker
      The Docker Platform is the industry-leading container platform for continuous, high-velocity innovation, enabling organizations to seamlessly build and share any application — from legacy to what comes next — and securely run them anywhere
      Microsoft Azure
      Azure is an open and flexible cloud platform that enables you to quickly build, deploy and manage applications across a global network of Microsoft-managed datacenters. You can build applications using any language, tool or framework. And you can integrate your public cloud applications with your existing IT environment.
      See all alternatives
      Decisions about Heroku, OpenShift, and Pivotal Web Services (PWS)
      Jerome Dalbert
      Jerome Dalbert
      Senior Backend Engineer at StackShare · | 7 upvotes · 18.7K views
      atGratify CommerceGratify Commerce
      Rails
      Rails
      Heroku
      Heroku
      AWS Elastic Beanstalk
      AWS Elastic Beanstalk
      #PaaS

      When creating the web infrastructure for our start-up, I wanted to host our app on a PaaS to get started quickly.

      A very popular one for Rails is Heroku, which I love for free hobby side projects, but never used professionally. On the other hand, I was very familiar with the AWS ecosystem, and since I was going to use some of its services anyways, I thought: why not go all in on it?

      It turns out that Amazon offers a PaaS called AWS Elastic Beanstalk, which is basically like an “AWS Heroku”. It even comes with a similar command-line utility, called "eb”. While edge-case Rails problems are not as well documented as with Heroku, it was very satisfying to manage all our cloud services under the same AWS account. There are auto-scaling options for web and worker instances, which is a nice touch. Overall, it was reliable, and I would recommend it to anyone planning on heavily using AWS.

      See more
      Russel Werner
      Russel Werner
      Lead Engineer at StackShare · | 19 upvotes · 238.9K views
      atStackShareStackShare
      React
      React
      Glamorous
      Glamorous
      Apollo
      Apollo
      Node.js
      Node.js
      Rails
      Rails
      Heroku
      Heroku
      GitHub
      GitHub
      Amazon S3
      Amazon S3
      Amazon CloudFront
      Amazon CloudFront
      Webpack
      Webpack
      CircleCI
      CircleCI
      Redis
      Redis
      #StackDecisionsLaunch
      #SSR
      #Microservices
      #FrontEndRepoSplit

      StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

      Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

      #StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

      See more