Stable and scalable PaaS platform
Overall Satisfaction with Red Hat OpenShift
We use OpenShift Fabric platform to manage hosting and deployment of our business applications. The platform handles management of environment configuration, pipelines and promotion paths of all our business applications contributing to the backbone of our trillion dollar revenue system. It is critical to our functioning and operations on technology
Pros
- Management of environment configuration, provisioning of pods and secrets is done in a foolproof, standard way so that multiple teams can identify and update it with minimal upkeep
- It has a large uptime ratio, meaning business applications downtime is usually not hampered
- It has an efficient way of scaling up and down pods to manage traffic and bandwidth
Cons
- Batch processing and streaming is not yet supported on the platform, and is supported by competitors like GCP
- Database hosting is handled separately, and thus cannot be maintained from the same pod
- It's not possible to create cross instance promotion paths
- Because of OpenShift's high uptime, there's been minimal business impact leading to thousands of dollars of revenue loss saved
- The easy setup and customizable configuration has greatly eased developer productivity by over 40% dev hours saved from manually setting up pods
- Secrets are securely maintained leading to regulatory compliance and saving face of the bank amidst severe data protection regulations
Because of OpenShift we have been able to deliver business applications at scale and managed to maintain heavy load across the platform
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
Red Hat OpenShift Feature Ratings
Using Red Hat OpenShift
40000 - OpenShift is used across multiple parallels - Technology teams, that use multiple layers and tools on OpenShift to deploy and test applications
Our production applications are run on OpenShift too, meaning production support teams regularly make use of logs, pods and config features
ITAO and tooling teams use it to monitor network usage and access control
Compliance teams use it to ensure adherence
Our production applications are run on OpenShift too, meaning production support teams regularly make use of logs, pods and config features
ITAO and tooling teams use it to monitor network usage and access control
Compliance teams use it to ensure adherence
5000 - We have at least one member per feature team who holds the technical and product know how to scale up/down pods, clear caches, view logs and help development teams
We have a dedicated DevOps team that works on provisioning namespaces and instances
We have dedicated ITAO teams that look at the overall figures, and grant accesses
We have a team exclusively that works with vendor teams to discuss on product roadmaps, rollouts and critical downtimes
We have a dedicated DevOps team that works on provisioning namespaces and instances
We have dedicated ITAO teams that look at the overall figures, and grant accesses
We have a team exclusively that works with vendor teams to discuss on product roadmaps, rollouts and critical downtimes
- OpenShift holds all of our applications down from Dev testing environments to production. It's literally the backbone of how the company runs
- OpenShift has allowed us to maintain, manage and scale applications with ease, while remaining compliant and secure
- OpenShift allows us to connect with existing tools like Bitbucket and Scribe to create a seamless flow for our applications to be tested end to end
- OpenShift has multiple features of logs, memories and detailed stats so we can look at cloud costs
- Bitbucket connects to Fabric to fetch config details, meaning we don't need to add configuration onto the Console, but just make a PR, and the rest is handled
- We have also enabled Spring Cloud to fetch configuration and variables, and that links well with Openshift too
- We have also leveraged slave namespace that integrate with jenkins to run pipelines for deployment
- Observability and metric logging is something we might get to see in coming years, as we have different tools we use right now
- We also expect stronger integration with Bitbucket, by allowing us to implement IaC (Infrastructure as code), to remove the dependency on OpenShift console
Comments
Please log in to join the conversation