Overall Satisfaction with Red Hat OpenShift
We have especially open enrollment, right where three, or four months we have a high traffic, especially on the enrollment side. So that's where we started the OpenShift but now it gets used across all the domains like claims, Medicare processing, and all the data for the application. So across all the applications we use. So I can say all business-critical applications run on the OpenShift. So one problem that, especially on the open enrollment we had scaling because those three, four months, the volume surge like 50 times, 200 times, right? The earlier challenge was to add the hardware and there are always delays that take a couple of months. But with OpenShift we can able to do it in just a few days. I think those scaling when we have a sudden burst of workload, was the major challenge for OpenShift was able to work on.
- I'll say the first one is obviously high availability, right? Because now application earlier, if you take any application that used to run WebSphere legacy platform, we'll have a side or B side. And that was not a true failover. But now with OpenShift we can add multiple ports, you can have four ports or eight ports, 10 ports how your business or application needs. So it's very what you call no downtime and literally there is no downtime.
- Another example you can say the patching now we have to patch due to compliance every month. So we do rolling updates so there is no downtime so I'll say highly available, scalable, another security is another great feature that we can use core os. So those are the key features
- So one thing I can think of is the cloud where we are going because now we are seeing workload going to AWS or Azure. I think there'll be a lot of integration needed from the OpenShift, how we can leverage more cloud services as the industry is moving toward that direction.
- One thing I can definitely mention, we are trying to do a database. First I'll start with the Redis in-memory database. So we had that installed on the openshift. But the way Redis in-memory works is they have their own DNS. And now with the state full set it was challenging when we patched and it did not work. We had to do a manual intervention. So those are challenges especially when you have state full workload like databases, how do you scale those, right? So those are big challenges that we can overcome.
- I'll say a lot of positive impact because when we started making this product aware to all the application domains in our business, they saw how easy to use. I mean we are giving a lot of control to the development team, how they can scale their application, how can they check the health of the application, and what action they can take if they are in any kind of failure or even meeting the business's SLA. So there are a lot of capabilities and those are really new features they can use. Those I think are a good use of OpenShift.
Do you think Red Hat OpenShift delivers good value for the price?
Yes
Are you happy with Red Hat OpenShift's feature set?
Yes
Did Red Hat OpenShift live up to sales and marketing promises?
Yes
Did implementation of Red Hat OpenShift go as expected?
Yes
Would you buy Red Hat OpenShift again?
Yes