Review: OpenShift 3 rocks Docker containers

Red Hat’s robust, easy-to-use, and highly scalable PaaS now builds on Docker, with some temporary limitations

Last year OpenShift 2 was my favorite open source PaaS. I said at the time, “OpenShift is outstandingly easy to use, manage, and install, and it presents little learning curve for developers familiar with Git and administrators familiar with Puppet. Enabling automatic horizontal scaling is as simple as checking a box in the application configuration. Automatic gear idling is enabled by default and allows for very high application density. And updating an application is as simple as doing a git push. For both developers and operators, OpenShift fulfills the promise of PaaS.”

Since then, OpenShift has undergone a complete rewrite to use Docker containers, instead of “cartridges” and “gears,” to deploy applications. In theory, that should make the OpenShift PaaS even simpler to use and give it an even larger pool of languages and applications, thanks to the containers already on Docker Hub. But how does it work in practice? Let’s find out.

To continue reading this article register now

Join the discussion
Be the first to comment on this article. Our Commenting Policies