We use the solution to split monolithic into microservices. I mostly use OpenShift as a Kubernetes distribution.
Red Hat OpenShift Platform Plus
Red Hat | 4.18 20250122-0Linux/Unix, Red Hat Enterprise Linux 9.4 - 64-bit Amazon Machine Image (AMI)
External reviews
288 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Enterprise grade Kubernetes
What do you like best about the product?
Simple usage and fast adoption from our teams
What do you dislike about the product?
Nothing special I dislike to mention. ..........
What problems is the product solving and how is that benefiting you?
Migrating from a VM world to a container enabled world
A stable and scalable solution for microservices and Kubernetes distribution
What is our primary use case?
What is most valuable?
I am impressed with the product's security features.
What needs improvement?
The tool lacks some features to make it compliant with Kubernetes.
For how long have I used the solution?
I am working with the solution for four years.
What do I think about the stability of the solution?
The tool is stable.
What do I think about the scalability of the solution?
The cloud version is scalable. The solution's on-prem scalability can be improved.
How are customer service and support?
The tool's support should be improved.
How would you rate customer service and support?
Positive
How was the initial setup?
The tool's deployment takes a matter of hours to complete. You need a team of three to four to maintain the solution.
What's my experience with pricing, setup cost, and licensing?
The product's support is expensive. I would rate the tool's pricing an eight out of ten.
What other advice do I have?
I would rate the solution an eight out of ten. The tool requires knowledgeable people to manage it.
Which deployment model are you using for this solution?
On-premises
Fast development, improved quality, and easy management
What is our primary use case?
We use it for container management. It's our container management platform for our financial systems.
How has it helped my organization?
It provides flexibility and efficiency. It helps us to design and deliver applications efficiently. We can modify our application in a smaller scope. We don't need to change the whole application.
It makes development fast because we can separate applications into different parts. We can deliver applications in different phases.
It has helped to improve the quality of our end products. It has reduced the project onboarding time by 20% to 25%.
What is most valuable?
I like OCP, and the management UI is better than the open-source ones.
The integration with 3scale is very good. We use that too.
What needs improvement?
The monitoring part could be better to monitor the performance. The automation part could also be better because we had a hard time integrating our application with OCP.
For how long have I used the solution?
I've been using this solution for about two years.
What do I think about the stability of the solution?
It's stable.
What do I think about the scalability of the solution?
It's scalable for one cluster. When it comes to multiple clusters, it could be better.
We have about 100 users who use this solution.
How are customer service and support?
Their enterprise support is okay, but sometimes, their response is slow. Their response is also not accurate sometimes. It's not right.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
I didn't use it, but my company used the PKS solution.
How was the initial setup?
It's straightforward. The setup took two to three days.
What other advice do I have?
Red Hat is quite okay as a partner for helping us create the platform that we need. They do help you. They also provide training.
We use Red Hat AMQ streams and 3scale, and its integration with other Red Hat solutions is okay. The advantage of using multiple products from the same vendor is that you can get help from one company. You don't have to go to multiple companies.
It gives me the security that I need, but I didn't evaluate the security much. There is another department that's responsible for that.
I would recommend this solution to others, and overall, I would rate it an eight out of ten.
Which deployment model are you using for this solution?
On-premises
Keys for us are the consolidation, ease of use, portability, and use of microservices
What is our primary use case?
We're going to deploy the entire core banking of the bank on the platform.
How has it helped my organization?
It helps us through consolidation, ease of use, portability, and because I can use microservices. It's like a one-stop shop for most of my containerized applications that are going to be deployed.
What is most valuable?
The most valuable features are that
- it's cloud agnostic
- the containerization and security features are outstanding.
The cloud-agnostic aspect means I can move to AWS, Google, or Azure. That means it is not a limitation. It gives me flexibility.
For running business-critical applications, on a scale of one to five, where five is the best, OpenShift is 4.8.
What needs improvement?
Room for improvement is around the offerings that come as a bundle with the container platform. The packaging of the platform should be done such that customers do not have to purchase additional licenses.
They should partner with Jenkins. It goes without saying that I need Jenkins for my CICD. If Jenkins comes with support, that's good. But if there is a licensed product, I need to secure that license and then I will get support.
Although the bundling with OCP is better than that offered by others, they can work more on it.
For how long have I used the solution?
We implemented OpenShift in January 2023, so about six months ago, but we have not fully used it. It's the first time that we've installed it, and we're yet to implement.
What do I think about the scalability of the solution?
It's pretty scalable because of the architecture. I don't see any issues in terms of scaling up or across. During our design phase, we had to scale across and as far as the design was concerned, it was pretty easy.
We can also scale it back. We can reduce or expand as per our needs.
In the future, it will be used by our entire bank, with between 8,000 and 10,000 users.
We intend to expand the usage but we have to wash our hands of the core banking system first, which itself is a huge system. Once we're done with that, we'll think about other applications.
How are customer service and support?
The forums and services are perfect. Excellent.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We did not have a previous container platform solution. We did try to build our own but it failed, badly. Building a container platform is not an easy task.
How was the initial setup?
The initial setup is in between straightforward and complex. It's not so easy but not that tough. But we do require a lot of training.
Our deployment took one month.
What about the implementation team?
Red Hat did most of it. We just provided them with the bare metal and away they went. It was a very time-bound project, and the Red Hat team was there. Our teams also worked with them. It was a collaborative exercise. On our side, there were 10 to 15 people involved, but there were five key people.
What other advice do I have?
The CodeReady Workspaces should help reduce time to market if I use the CICD pipelines. That's what we aim for, and that's what the container platform is built for. That's something that goes without saying.
We're using Red Hat Linux across the bank for servers. We will use quite a number of Red Hat products during our core banking deployment, including AMQ, Process Automation Manager, and a couple of other products that are bundled with OCP.
The integration is something that is out of the stack. It's more of a middleware conversation and the middleware for us is an IPaaS. It's less about the stack and more about the application. I don't think there are any issues communicating via APIs. And the access management is pretty adequate. I can plug in any IM or document archival solutions. It's pretty easy to integrate.
Red Hat, as a vendor, has shared ample information with us to help us make decisions. That is where a partner comes into play and we're pretty happy with Red Hat.
Which deployment model are you using for this solution?
On-premises
Best Ui tool for deplyment
What do you like best about the product?
Best tool for monitoring and deployment.
What do you dislike about the product?
Raw Logging is not proper in this tool.
What problems is the product solving and how is that benefiting you?
Deployment is easy in openshift platorm and it is provide best user interface.
Application Development is fairly easy although you will need to read documentation
What do you like best about the product?
It's fairly easy to use when it's well set up by the administrators. Documentation is very complete. Creation and management of volumes and persistent volumes. Pod log is fairly useful for debugging.
What do you dislike about the product?
Secrets management need more user-friendly editing. Large amount of pipelines in the same project makes it hardly manageable. Pod log randomly skips entries.
What problems is the product solving and how is that benefiting you?
Moving out from a decaying IaaS architecture allowing us to cut costs from overhead. Simplifying and reducing time of the deployment procedures and enhancing the development team work.
Red Hat OpenShfit Platform Review
What do you like best about the product?
The best part of the RedHat OpenShift Platform is the UI which makes it easy even for a new person to use. Unlike other Container platforms, this UI feature is very helpful in managing the application.
What do you dislike about the product?
It is an on-premise solution which makes it difficult to put a lot of capital upfront for setting up the cluster, which makes it more expensive when compared to other cloud-based Kubernetes platforms. With the growing cloud trend, the organizations will keep looking for a more cost-effective platform instead of investing massive capital into OpenShift.
What problems is the product solving and how is that benefiting you?
We managed our platform efficiently with OpenShift and were able to deploy applications with much ease. With the UI, we could solve any deployment-related issues much faster than other Kubernetes platforms, which has to be through CLI.
Will recommend it to others, as Openshift provide several others features which plain K8S doesn't
What do you like best about the product?
Source to Image functionality, User-friendly UI
What do you dislike about the product?
Nothing to dislike at this moment. It has all the extra features that we have to add to plain K8S
What problems is the product solving and how is that benefiting you?
Mainly container orchestration.
Logging & Monitoring also comes pre-installed in Openshift
Logging & Monitoring also comes pre-installed in Openshift
Recommendations to others considering the product:
Will recommend it to others, as Openshift provide several others features which plain K8S doesn't
Redhat openshift platform
What do you like best about the product?
We can integrate with Azure cloud using Azure redhat openshift
What do you dislike about the product?
It doesn't have much documents to review
What problems is the product solving and how is that benefiting you?
Solved containerized workloads
Completely scalable orchestrated platform
What do you like best about the product?
Scalability and easy config changes and controls
What do you dislike about the product?
There are no such cons in redhat openshift
What problems is the product solving and how is that benefiting you?
Web service deployments and agile adoption is very easy with openshift
showing 41 - 50