CloudFoundry is a free, open source cloud computing platform supported by the non-profit CloudFoundry. It is not tied to any particular cloud service, but can be self-hosted or run on any cloud service preferred.
N/A
Red Hat OpenShift on IBM Cloud
Score 8.9 out of 10
N/A
Red Hat OpenShift on IBM Cloud is a comprehensive service that offers fully managed OpenShift clusters, on IBM Cloud platform. It is directly integrated into the same Kubernetes service that maintains 25 billion on-demand forecasts daily at The Weather Company.
RedHat OpenShift is not only suited for IBM Cloud but can run in ANY cloud. We installed in Azure Cloud, for example. It can also run on Linux servers or a Power 9 machine. It is built for multi-cloud or on-prem environments. IBM support provides such excellent guidance in the installation and configuration that no other product on the market can beat it.
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
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.
While Docker shines in providing support for volumes and stateful instances, Cloud foundry shines in providing support for deploying stateless services. Heroku shines in integrating with Git and using commits to git as hooks to trigger deployments right from the command line. But it does not provide on-premise solution that Cloud foundry provides.
We evaluated a number of potential solutions and ultimately chose Red Hat OpenShift because it was compatible with our existing technology. Time and costs savings have been realized throughout the company since we implemented Red Hat OpenShift, and the IT department has been freed up to focus on activities that are more valuable.
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.
