We performed a comparison between Cloud Foundry, Google Compute Engine, and OpenShift based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Amazon Web Services (AWS), Oracle and others in PaaS Clouds."IBM is the only vendor to offer integration with blockchain for smart contract development."
"Cloud Foundry builds the runtime environment directly without requiring dependency management from the user."
"My favorite component of IBM's solution is Node-RED, which greatly shortens the amount of time required to develop, test, and deploy new applications."
"It's the most engineer-friendly product compared to Amazon AWS or Azure."
"The main motive for choosing Google Compute Engine is pricing."
"The support for ephemeral instances has been particularly valuable for me. It allows me to significantly reduce costs for temporary virtual machines by automatically destroying them once they are no longer needed, which can result in cost savings of up to 90 percent. Additionally, the solution is easy to use."
"The most valuable feature is auto-scaling."
"Google is managing all hardware. You don't need to provision or pre-provision your computer engine."
"Everything is simple and useful. The initial setup is not challenging."
"The solution is readily available, and software engineers can provision it. It is scalable and allows self-service."
"One of GCE's best features is the managed instance groups."
"The security is good."
"Security is also an important part of this solution. By default, things are running with limited privileges and securely confined to their own resources. This way, different users and projects can all use the same infrastructure."
"Provides support throughout the whole platform."
"OpenShift is based on Kubernetes and we try to use all the Kubernetes objects of OpenShift. We don't use features that are specific to OpenShift, except internal certificates for the services. The one feature that is missing from Kubernetes and that is really useful in OpenShift is the lifecycle of the cluster and the ease of installation. We use VMware and VMware integration internally with the OpenShift installer, which is very good. With OpenShift it's easy to spin up or scale out a cluster."
"Self-provisioning support saves a lot of time and unnecessary work from the system administrator who can use this time to run and monitor the infrastructure. For the developer, this means less time waiting for the provisioning and excellent flexibility for development, testing, and production. Also, in such systems it is easy for developers to monitor applications even after deployment."
"Key features are WildFly, because it standardizes infrastructure and the git repository and docker. Git is essential for source code and Docker for infrastructure."
"The most valuable feature is the auto scalers for all microservices. The feature allows us to place request limits and it is much cheaper than AWS."
"Its security is most valuable. It's by default secure, which is very important."
"After the initial excitement period with Node-RED is over, you crave the need of additional integrations to third-party services."
"In IBM Cloud, the product has been deprecated in favor of Kubernetes, which is a more complicated infrastructure to manage."
"Google Compute Engine needs to have multi-region support. It would also be nice to have a tracking mechanism."
"It would be better if there was an option to change the background. Like in Gmail, there's an option to change your theme."
"Google Compute Engine does not have many options at a lower tier level. If they had more options it will be better. For example, Amazon AWS or Microsoft Azure, have more options and different types of instances, of VMs we can select."
"It has some limitations. For example, you don't get through layer two connectivity. So I've had some difficulty deploying custom VMs. For example, you can't deploy a KVM file to file directly on GCP."
"I would like to improve the solution’s UI while deploying a container. It is sometimes hard to figure out the container’s details and format that you want to deploy. The tool does not give you a guide to find out the error and why the container is not starting up which could be because you have configured it wrong. This is always a hit on the setup."
"The biggest problem is that it's got a very archaean and complex security environment that has to be very carefully set up and is easy to break."
"It is not very user-friendly for non-experienced users"
"The licensing process is not a very straightforward process."
"My team has found some bugs in OpenShift due to continuous integration, and this is an area for improvement in the platform. RedHat should fix the bugs. Another area for improvement in OpenShift is that upgrading clusters can be challenging, resulting in downtime. Application support also needs improvement in OpenShift because the platform doesn't support all applications in the cloud. I'd like upgraded storage in the next release of OpenShift, especially when I need to do a DR exercise. It would also be good if the platform allows mirroring with another cluster, or more portability in terms of moving applications to another cluster."
"The software-defined networking part of it caused us quite a bit of heartburn. We ran into a lot of problems with the difference between on-prem and cloud, where we had to make quite a number of modifications... They've since resolved it, so it's not really an issue anymore."
"The metrics in OpenShift can use improvement."
"The monitoring part could be better to monitor the performance."
"An enhancement to consider for the future might involve incorporating a comprehensive solution for CI/CD tailored specifically for OpenShift."
"OpenShift can improve monitoring. Sometimes there are issues. Additionally, the solution could benefit from protective tools if something was to happen in our network."
"Autoscaling is a very unique feature, but it could be useful to have more options based on traffic statistics, for example, via Prometheus. So, there should be more ready solutions to autoscale based on specific applications."
"We experienced issues around desktop security, that stopped us implementing a new feature that had been developed."
