We are using OpenShift as a microservice platform.
Head Of Department Digital Center of Excellence at Pegadaian
Useful containers and reliable
Pros and Cons
- "The most valuable feature of OpenShift is the containers."
- "OpenShift can improve monitoring. Sometimes there are issues. Additionally, the solution could benefit from protective tools if something was to happen in our network."
What is our primary use case?
What is most valuable?
The most valuable feature of OpenShift is the containers.
What needs improvement?
OpenShift can improve monitoring. Sometimes there are issues. Additionally, the solution could benefit from protective tools if something was to happen in our network.
In a new release of OpenShift, they should add Kibana, Grafana, and Elasticsearch.
For how long have I used the solution?
I have been using OpenShift for approximately two years.
Buyer's Guide
Red Hat OpenShift
December 2024
Learn what your peers think about Red Hat OpenShift. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
824,053 professionals have used our research since 2012.
What do I think about the stability of the solution?
OpenShift is stable. However, I feel it could be better but the local implementor is not giving us all the information.
What do I think about the scalability of the solution?
We use OpenShift on a daily basis. We have one engineer for the operation and a pre-engineer for monitoring. Additionally, we have more than five to handle the daily work.
How are customer service and support?
We are using a local vendor for the support. They can handle level one and two support when we have issues.
How was the initial setup?
The initial setup of OpenShift is complex. We have two types we do, but active active does not work, only active passive does.
What about the implementation team?
We used a local vendor to do the implementation and maintenance.
What other advice do I have?
I rate OpenShift an eight out of ten.
Which deployment model are you using for this solution?
Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Assistant to Vice President at a consultancy with 10,001+ employees
Good support, scalable, and helpful support
Pros and Cons
- "The scalability of OpenShift combined with Kubernetes is good. At least from the software standpoint, it becomes quite easy to handle the scalability through configuration. You need to constantly monitor the underlying infrastructure and ensure that it has adequate provisioning. If you have enough infrastructure, then managing the scalability is quite easy which is done through configuration."
- "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."
What is our primary use case?
We use OpenShift mainly for building middleware services and web applications. All the applications we have transformed on the microservices architecture have been deployed on OpenShift.
What needs improvement?
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.
Making use of features, such as serverless technology we easily integrate these services with OpenShift. It would be a win-win, because then you can choose the best of all the worlds, and then build your solution.
For how long have I used the solution?
I have used OpenShift within the last 12 months.
What do I think about the stability of the solution?
OpenShift is a stable solution.
What do I think about the scalability of the solution?
The scalability of OpenShift combined with Kubernetes is good. At least from the software standpoint, it becomes quite easy to handle the scalability through configuration. You need to constantly monitor the underlying infrastructure and ensure that it has adequate provisioning. If you have enough infrastructure, then managing the scalability is quite easy which is done through configuration.
We have approximately thousands of users using the solution. The business applications that we build, our customers use them regularly, this includes the banking and insurance applications.
How are customer service and support?
All the platforms that we have, whether it is Pivotal, VMware, Red Hat, Microsoft, or Amazon, are partners or we have an alliance with them. We regularly speak to them and we discuss with them the challenges we face. We have a good relationship with the support.
How was the initial setup?
The initial setup on the OpenShift platform took us a long time to complete for the whole department. It took approximately one and a half months to set it up properly.
Once the implementation was complete we started looking at how we can achieve reusable scripts for the developers. In a way that they can create the scripts in a quick fashion, instead of them doing the configuration and deployment themselves. It takes time for the implementation, and then it's complex overall too. Once you learn it, then it's quite easy.
What about the implementation team?
The team we have is small for maintenance and support. We have approximately six people managing the whole platform for the entire department. Earlier on, there were more, but the platform has matured, and then the number of applications the platform used to run is going down because they're being moved to Microsoft Azure and Amazon AWS. We keep the team approximately four people who will manage the platform for the next couple of years for the whole department. After that, everything will be on either Microsoft Azure or Amazon AWS.
What other advice do I have?
We are in the phase of moving out of OpenShifh to cloud-native services of Microsoft Azure or Amazon AWS.
If anybody is looking for a solution that can work on-premise as well as on the cloud and gives the flexibility of not tying the solution to the underlying platform, then OpenShift is one of the popular choices you can make.
I rate OpenShift an eight out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer: Integrator
Buyer's Guide
Red Hat OpenShift
December 2024
Learn what your peers think about Red Hat OpenShift. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
824,053 professionals have used our research since 2012.
Head of Architecture at a financial services firm with 10,001+ employees
An easily scalable solution offering good cluster management and continuous improvements with upgrades
Pros and Cons
- "We have found the cluster management function to be very good with this product."
- "We experienced issues around desktop security, that stopped us implementing a new feature that had been developed."
What is our primary use case?
We use the solution for container orchestration and management.
What is most valuable?
We have found the cluster management function to be very good with this product. Also, each new version of the product has made upgrading easier and faster to carry out.
What needs improvement?
We experienced issues around desktop security, which stopped us from implementing a new feature that had been developed. This needs to be improved in order to expand the usage of the product.
For how long have I used the solution?
We have been working with this solution for around two and a half years.
What do I think about the stability of the solution?
We have found the solution to be very stable.
What do I think about the scalability of the solution?
We have found the solution to be very scalable during our time using it, and we now have a large number of transactions passing through the product.
How are customer service and support?
The technical support is good, but they have been slow to respond in the past. The issues were resolved effectively, but it took some time for this to happen.
How would you rate customer service and support?
Positive
How was the initial setup?
The initial setup of the solution was hard, and took around three months to deploy completely.
What about the implementation team?
We used a third-party vendor for our implementation, and they were very knowledgeable.
What's my experience with pricing, setup cost, and licensing?
Depending on the extent of the product use, licenses are available for a range of time periods, and are renewable at the end of the period.
What other advice do I have?
I would recommend that organizations pay a lot of attention to the initial design and setup of the solution to ensure that it is optimized for their needs, as it isn't easy to make changes once this is complete.
I would rate this solution an eight out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior (Consultant) Software Engineer at a healthcare company with 10,001+ employees
It is simple to build configurations and deploy your changes and promote them to different environments.
What is most valuable?
Application deployment using YAML with Docker containers, creating services and providing routes. It is simple to build configurations and deploy your changes and promote them to different environments.
How has it helped my organization?
We are better able to manage application development and promoting from development to staging to production using configurations.
What needs improvement?
They could provide a template for application deployment and building services and routes so it can all be promoted as a bundle if needed.
This would allow the promotion of the application (which includes the Spring Boot jar, the Kubernetes Service, the Kubernetes Route, dependencies such as properties or secrets) from development through the production environment.
For how long have I used the solution?
We have been using the solution for four years.
What do I think about the stability of the solution?
We did not encounter any issues with stability.
What do I think about the scalability of the solution?
We did not encounter any issues with scalability.
How are customer service and technical support?
I did not use the technical support but I do look up plenty of resources on the OpenShift blog which is useful.
Which solution did I use previously and why did I switch?
We were using individual Tomcat on VMS for a high availability and scalable architecture.
How was the initial setup?
The setup is straightforward if you understand concepts from a Kubernetes cluster development. I have done CoreOS cluster development so I am familiar with much of the setup.
What's my experience with pricing, setup cost, and licensing?
I would try the online public OpenShift instance first and see if it is something that would provide benefit to each enterprise architecture and then go on from there.
Which other solutions did I evaluate?
We have found RedHat OpenShift to provide the best solution and ease of use.
What other advice do I have?
Try out OpenShift or read up on it first to see the benefits. Also build a Kubernetes cluster yourself to know what goes on under the hood in OpenShift.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Solution Architect at a manufacturing company with 11-50 employees
Easy-to-use product with valuable features for integrating CI/CD pipelines and repositories
Pros and Cons
- "It is a stable platform."
- "The product’s integration with Windows containers and other third-party products needs improvement."
What is our primary use case?
We use OpenShift for the deployment of microservices architecture and containerizing applications.
What is most valuable?
The product is easy to use. It has valuable features for integrating CI/CD pipelines, repositories, and support from open-source communities.
What needs improvement?
The product’s integration with Windows containers and other third-party products needs improvement.
For how long have I used the solution?
We have been using OpenShift for three to four years.
What do I think about the stability of the solution?
It is a stable platform.
What do I think about the scalability of the solution?
The product is expensive to scale for smaller businesses in an on-premise environment. They can instead opt for a public cloud setup. The enterprises that can afford the cost should only opt for it if they have a specific use case or want to transform applications.
How are customer service and support?
We receive remote and on-call support services on purchasing an enterprise support subscription.
How was the initial setup?
The implementation is not as straightforward as VMware products. It requires prior experience for easier deployment.
What's my experience with pricing, setup cost, and licensing?
The product’s pricing is expensive. It has the biggest market share right now as a containerization platform. It is the highest-selling product.
Which other solutions did I evaluate?
Vanilla doesn’t have essential features like CI/CD integration, repositories, and community, similar to OpenShift.
What other advice do I have?
I rate OpenShift a nine out of ten. It is a wonderful product. I advise others to choose the environment size properly. You can deploy it on a public cloud and not necessarily on-premises. You can decide depending on the workload and data localization requirements.
Disclosure: My company has a business relationship with this vendor other than being a customer: Reseller
IT Specialist at a government with 10,001+ employees
Stable and scalable platform used for containerization and to manage different applications in a simple way
Pros and Cons
- "The most valuable aspect of this solution is the great customer service and the ability for our team to get assistance when we need it."
- "This is a fairly expensive solution."
What is our primary use case?
We use this solution as part of our containerization so that we can manage different applications in the system. We use it to make the CICD pipeline and integrations smoother.
How has it helped my organization?
This solution really makes a lot of the containerization work really simple and reduces complexity which is important for us.
What is most valuable?
The most valuable aspect of this solution is the great customer service and the ability of our team to get assistance when we need it.
For how long have I used the solution?
This solution has been used by our business for three years.
What do I think about the stability of the solution?
This is a stable solution.
What do I think about the scalability of the solution?
This is a scalable solution.
How are customer service and support?
I would rate the support for this solution a nine out of ten.
How would you rate customer service and support?
Positive
What was our ROI?
It seems like we're getting a pretty high return on our investment because of our ability to navigate, integrate and migrate across platforms. We have gone from one cloud platform to a new platform and that has been almost seamless and exceptionally simple.
What's my experience with pricing, setup cost, and licensing?
This solution is fairly expensive but comes at an average cost compared to other solutions in the market.
What other advice do I have?
I would rate this solution a ten out of ten because this solution has been able to adapt to our needs as we continue to innovate.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
Disclosure: I am a real user, and this review is based on my own experience and opinions.
SAFe System Cloud Architect at BIT
Robust platform with valuable automation capabilities
Pros and Cons
- "I would recommend Red Hat OpenShift, especially for its automation capabilities."
- "The platform's documentation could be more comprehensive to cover the full spectrum of user needs. Sometimes, achieving specific goals is challenging due to a lack of detailed guidance."
What is our primary use case?
We use the product primarily for CI/CD activities across different platforms using Argo CD and Tekton to deliver applications.
What needs improvement?
The platform's documentation could be more comprehensive to cover the full spectrum of user needs. Sometimes, achieving specific goals is challenging due to a lack of detailed guidance.
For how long have I used the solution?
I've been using Red Hat OpenShift for about six months.
What do I think about the stability of the solution?
I would rate the product stability as an eight.
What do I think about the scalability of the solution?
The platform is scalable.
How was the initial setup?
I'm not directly involved in the deployment process, but from what I've observed, it seems manageable.
What other advice do I have?
I would recommend Red Hat OpenShift, especially for its automation capabilities. It's a solid platform, backed by reputable companies like IBM, ensuring stability and security.
I rate it an eight.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Last updated: Jun 1, 2024
Flag as inappropriateConsultant at Pi DATACENTERS
A stable platform for container workload deployment with great GUI functionality
Pros and Cons
- "There is a quick deployment of the application, and we can scale out efficiently."
- "There is no orchestration platform in OpenShift."
What is our primary use case?
We are modernizing our data staging environment and moving from traditional virtualization. A year ago, we started deployment with the container. We moved to OpenShift because we wanted to modernize the application with quick deployment and portability and explore the users of that particular containerization feature.
How has it helped my organization?
There is a quick deployment of the application, and we can scale out efficiently with the help of OpenShift. We can run containers quickly.
What is most valuable?
The GUI functionality in the black command is great because, in Docker, we get only CLI. In the OpenShift, we get the GUI interface, and we can manage the GUI itself.
What needs improvement?
There is no orchestration platform in OpenShift, but we do in Kubernetes. So, it'll be great to get an orchestration platform like Rancher or Kubernetes.
For how long have I used the solution?
We have been using this solution for one year. We were using version 4.6, and we upgraded to 4.10. It is deployed on-premises.
What do I think about the stability of the solution?
OpenShift is more stable than the Docker Platform. As a result, it is a stable platform for container workload deployment.
What do I think about the scalability of the solution?
It is very scalable. We have deployed approximately 30 plus apps with the help of OpenShift. We require one senior system engineer for maintenance. We plan to increase the workload on OpenShift once we get a staging environment.
Which solution did I use previously and why did I switch?
We evaluated Docker before moving to OpenShift.
How was the initial setup?
The initial setup was a bit complex because we needed to configure the work upload and the master mode. We also need to run many containers inside to run the OpenShift Platform, which is complex. The deployment was done in-house with the help of Red Hat as an OEM.
What was our ROI?
It helps us utilize our resources conservatively and minimize our footprint. We can reduce the virtual machine and move it to the container, so it saves the computer, memory, and network resources.
What's my experience with pricing, setup cost, and licensing?
We get a bundled cost with one of our product suites, but I am unsure of the exact costs.
What other advice do I have?
I rate the solution an eight out of ten. Regarding advice, I would suggest working on your application to migrate it. For example, if you go with OpenShift, you need to convert your application virtual machine to the container version. I would also recommend networking inside the load balancer and the routing capability.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free Red Hat OpenShift Report and get advice and tips from experienced pros
sharing their opinions.
Updated: December 2024
Popular Comparisons
Microsoft Azure
Amazon AWS
Oracle Cloud Infrastructure (OCI)
VMware Tanzu Platform
Google Cloud
SAP Cloud Platform
Salesforce Platform
Pivotal Cloud Foundry
IBM Public Cloud
Google App Engine
Virtuozzo Application Platform
IBM Cloud Private
Cloud Foundry
Azure Red Hat OpenShift
Buyer's Guide
Download our free Red Hat OpenShift Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- How does OpenShift integrate with other products - Red Hat and non-Red Hat ones?
- What OpenShift plan are you paying for and why have you chosen it?
- What is Red Hat OpenShift used for at your organization?
- How to install an Elasticsearch cluster (with security enabled) on OpenShift?
- How does OpenShift compare with Amazon AWS?
- Which would you recommend - Pivotal Cloud Foundry or OpenShift?
- What are the differences between AKS and OpenShift?
- Looking for a cost comparison evaluation for PaaS platforms
- When evaluating a Platform as a Service (PaaS), what aspects do you think are the most important to look out for?
- Pros/cons of Rackspace vs. other leading vendors?
Interesting review - although I am not sure what is meant by "There is no orchestration platform in OpenShift." As it is an orchestration platform!