CloudFoundry vs OpenShift

• Support for Orgs and Spaces that allow for managing users and deployables within a large organization.
• Easy deployment, deploying code is as simple as executing single line from CLI, thanks to build-packs.
• Solid and rich CLI, that allows for various operations on the instance.
• Isolated Virtual Machines called Droplets, that provide clean run time environment for the code. This used to be a problem with Weblogic and other application servers, where multiple applications are run on the same cluster and they share resources.
• SSH capability for the droplet (isolated VM's are called droplets), that allows for real time viewing of the App code while the application is running.
• Support for multiple languages, thanks to build-packs.
• Support for horizontal scaling, scaling an instance horizontally is a breeze.
• Support for configuring environment variable using the service bindings.
• Supports memory and disk space limit allocation for individual applications.
• Supports API's as well as workers (processes without endpoints)
• Supports blue-green deployment with minimal down time

Read full review

• Pre built cartridges, giving a huge range of software ready to go. Reduces the amount of time required to get up and running.
• Integration with GIT was an advantage, cloning the repo and making changes was straight forward.
• Speed, creating an environment in minutes, ready to deploy.

Read full review

• Does not support stateful containers and that would be a nice to have.
• Supports showing logs, but does not persist the logs anywhere. This makes relying on Cloud Foundry's logs very unreliable. The logs have to be persisted using other third party tools like Elk and Kibana.

Read full review

• I would like to see a public cloud using OpenShift and Docker integration. I am not aware if this is already available now.
• I would like to see a tool that can help with extracting log files from the remote server like it being available on a Samba shared folder. And other applications that want to scan for keywords in the application log can check if there have been any errors or exceptions thrown by the application.

Read full review

• Positive impact, since it simplifies the deployment time by a huge margin. Without cloud foundry, deploying a code needs coordination with infrastructure teams, while with cloud foundry, its a simple one line command. This reduces the deployment time from at least few hours to few minutes. Faster deployments promote faster dev cycle iterations.
• Code maintenance such as upgrading a Node or Java version is as simple as updating the build-pack. Without cloud foundry, using web logic, the specific version only supports a specific version of Java. So updating the version involves upgrading the version of web logic that needs to involve few teams. So without cloud foundry, it takes at least few days, with cloud foundry, its a matter of few mins.
• Overall, happier Developers and thats harder to quantify.

Read full review

• Cost - OpenShift is extremely inexpensive. I use a free account for Dev and QA. For production, I am planning on using a low cost paid subscription.
• Time - You can get your application up and running in minutes so if you find that the service is not for you, you don't have much to lose.

Read full review