Whether in a public cloud or in a private data center, OpenShift keeps you productive
December 16, 2014

Whether in a public cloud or in a private data center, OpenShift keeps you productive

Isaac Christoffersen | TrustRadius Reviewer
Score 10 out of 10
Vetted Review

Software Version


Modules Used

  • Both the OpenShift Online and Enterprise versions.
  • Java, Ruby, Php, Node JS Apps
  • Wordpress, Drupal, Ghost, OwnCloud Instant Apps

Overall Satisfaction with OpenShift

We leverage OpenShift in a number of ways. First, we use it to support the Academic institutions by setting up environments for students to access course applications. Second, we use it to host our Sales Automation and quote generation tools. Finally, we leverage it to support development environments and enable developer self-service.
In addition to being a consumer, we also are a consulting company where we advise companies as to the use and implementation of OpenShift and PaaS solutions within there environment. We help them identify which applications are ideal fits and which ones should be avoided. In addition, we have worked with other partner companies to bring their products to the OpenShift environment. ownCloud is one such company where we not only created the instant application to be deployed in the environment, but also developed an on-premise Dropbox alternative for companies concerned about data ownership.
  • Ability to rapidly create application hosting environments
  • Security-first mindset with SELinux and limited ports open by default
  • Rich ecosystem of tools, frameworks, and languages. While most PaaS environments are just now moving to a Polyglot platform, OpenShift has been doing it from day one.
  • Improved monitoring of the stack. Difficult to see how the different layers can be impacted and correlate events.
  • OpenShift + Docker deployment strategies - ability to move application workloads between different deployments such as developer environments, other cloud providers.
  • More commercial supported applications similar to Drupal, Wordpress, EnterpriseDB, MongoDB, AppDynamics, etc.
  • Stability of our hosted applications as we were able to not focus on infrastructure and direct resources to the applications itself.
  • Ability to size workloads more appropriately to the application needs. If an application is only needed once a week, we can spin it down until its needed. This helps with aligning resource consumption.
  • Ability to quickly spin up Proof of concepts as well as replicate standalone environments faster. For example, in support of one our academic institution clients, we were able to quickly stand up 10 environments for a class in a matter of minutes
Leveraged Heroku for quick development environments. The tooling was comparable to OpenShift but the cost was much higher. In addition, being able to deploy the same applications in OpenShift Online and in the on premise Enterprise version is a benefit as it allows for cloud-bursting scenarios.
Leverage OpenShift Online constantly at both the free and paid tiers. While AWS is convenient, it often brings more administration than I want to deal with for a quick application (i.e. Drupal or Wordpress blog). OpenShift also simplifies the DNS registration and ability to share application environments with team members.
OpenShift is not suited for database hosting scenarios like Oracle RAC. Best suited for stateless web applications, but if there is shared data, a distributed cache is probably about the best way to handle that.