We performed a comparison between Cloud Foundry, Mendix, 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."Cloud Foundry builds the runtime environment directly without requiring dependency management from the user."
"IBM is the only vendor to offer integration with blockchain for smart contract development."
"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."
"You can scale the solution."
"The solution is stable."
"I think that the workflow and automation features are quite good."
"It is low code, where the developers can still develop in Java. That to us is very appealing."
"They are leading in the smart manufacturing, and connectivity space."
"The pricing is very clear, with no hidden fees."
"It is a brilliant solution."
"The features that I have found most valuable with Mendix are its business process management and its minimal low code, both from an interface perspective and from a process perspective."
"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 initial setup is simple, and OpenShift is open-source, so it's easy to install on any cloud platform."
"This solution helps us to account for peak seasons involving higher demand than usual. It also gives us confidence in the security of our overall systems."
"It is a stable platform."
"What I like best about OpenShift is that it can reduce some of the costs of having multiple applications because you can just move them into small container applications. For example, applications don't need to run for twenty days, only to be used up by Monday. Through OpenShift, you can move some of the small applications into any cloud. I also find the design of OpenShift good."
"I am impressed with the product's security features."
"Great integration with Jenkins for constant integration and development. Supports all the major languages and environments - PHP, Java, Node.js, Ruby, etc."
"Scaling and uptime of the applications are positives."
"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."
"Mendix needs to think about itself offering machine learning and artificial intelligence."
"My understanding is that, if you are not using the free version, it is very expensive."
"An improvement I would like to see is the ability to version manage independent modules. Their version management for software repositories must be better. It's good and you can do it, but it needs work."
"While the community is great, they need to work on making their direct technical support services better."
"The platform still has many areas for improvement. If I compare apples to apples, the PWA features of Mendix could be improved, for example, I wouldn't recommend creating a B2C or B2B marketplace or web portals on Mendix, but there's a tendency for people to still do it through the systems provided by my company, particularly implement B2B or B2C marketplace, versus using eBay or Shopify. On the web portal front, Mendix still needs to improve."
"Mendix is great for internal applications but not so great for a public-facing interface. It lacks a proper directory structure for public use. The URL will not change from page to page unless a deep link is created for each page. That makes it difficult to bookmark pages in the browser to view later on."
"You need experienced programmers and developers to understand this solution."
"I would also like to see automatic adjustment to the Java Heap, whenever an application load becomes too much for the application. It could also use hot database replication."
"It could use auto-scaling based on criteria such as transaction volume, queue backlog, etc. Currently, it is limited to CPU and memory."
"This is a fairly expensive solution."
"Its virtual upgrades are time-consuming."
"Latency and performance are two areas of concern in OpenShift where improvements are required."
"One glaring flaw is how OpenShift handles operators. Sometimes operators are forced to go into a particular namespace. When you do that, OpenShift creates an installation plan for everything in that namespace. These operators may be completely separate from each other and have nothing to do with each other, but now they are tied at the hip. You can't upgrade one without upgrading all of them. That's a huge mistake and highly problematic."
"An enhancement to consider for the future might involve incorporating a comprehensive solution for CI/CD tailored specifically for OpenShift."
"OpenShift could improve by providing the ability to integrate with public cloud platforms. This way we can easily use the services that these platforms offer. For instance, Amazon AWS. However, all the three major hyper-scalers solutions offer excellent DevOps and CI/CD tooling. If there was an easy way to integrate with them it would be beneficial. We need a way to easily integrate with the monitoring and dashboard services that they provide."
"We want to see better alerting, especially in critical situations requiring immediate intervention. Until we go to the dashboard, it can be challenging to quickly recognize that there's an issue for us to deal with. Therefore, a popup of the event or a tweaked GUI to catch our attention when it's alerting would be a welcome change. Everything else is good. We don't need any additional features. From the operations perspective, as an administrator, there is nothing concerning."
