Executive Manager - Strategy & Enterprise Architecture Office at Al Rajhi Bank
Real User
Top 20
2024-02-16T15:41:04Z
Feb 16, 2024
In our DevOps environment, we've encountered a unique challenge as our mainframe is currently not integrated into the DevOps pipeline. However, for the rest of our OpenShift platform, we've successfully implemented a DevOps workflow using Jenkins, GitHub, etc. I rate the overall product an eight out of ten.
Senior Global IT Infrastructure Manager at a manufacturing company with 10,001+ employees
Real User
Top 20
2023-11-01T10:08:35Z
Nov 1, 2023
Our organization used IBM Cloud Private for compliance because it allows us to manage to the lowest layer. We have control of the ESXi. In GCE, we have no control over ESXi. I would look for other solutions. IBM Cloud Private does monitor the environment. They just give you a set of provisions from their portal. I use IBM Cloud Private due to this compliance reason. But it makes no difference because I need to build all these BPCs and subscribe to all these links to connect. If I host it within, I think it's a lot simpler. I rate IBM Cloud Private a five out of ten.
Head of Product Development at a comms service provider with 1,001-5,000 employees
Real User
Top 20
2023-10-06T15:18:09Z
Oct 6, 2023
There are a couple of guidelines that I would suggest to consider when evaluating IBM Cloud Private. Firstly, it's important to determine your specific goals. If you're looking to establish a microservices-based architecture, there are alternative options in the market that might be more cost-effective. Secondly, ease of use is a crucial factor. There are other solutions on the market, such as VMware Tanzu, that provide additional benefits, including a reporting system, alarms, and monitoring tools under the same license, making it more operationally efficient. It should be noted that IBM has reportedly stopped selling it in certain regions, so I would suggest paying attention to that as well. Furthermore, the flexibility of buying individual software components independently may be more attractive than being tied to the bundled offerings in ICP. Lastly, if cost is a concern, open-source solutions like plain Kubernetes (K8s) offer more budget-friendly alternatives. You can select the features and licenses that fit your financial constraints. Overall, I would rate IBM Cloud Private a six out of ten because of performance concerns. It struggled when subjected to high traffic loads, and troubleshooting was challenging.
I think this IBM solution is the best for the industry because they support legacy systems, and since we're dealing with regulations, it's the best way for us to stay safe. The stability of the system is more important than anything. From a financial point of view, I recommend it. I rate the solution seven out of 10.
Platform-as-a-service (PaaS) is a kind of cloud computing service in which, rather than having to build and maintain their own infrastructure, a client is able to develop, run, and manage applications on a platform that is provided by a third-party provider. The provider hosts both software and hardware, freeing the client from having to install and handle them in-house.
In our DevOps environment, we've encountered a unique challenge as our mainframe is currently not integrated into the DevOps pipeline. However, for the rest of our OpenShift platform, we've successfully implemented a DevOps workflow using Jenkins, GitHub, etc. I rate the overall product an eight out of ten.
Our organization used IBM Cloud Private for compliance because it allows us to manage to the lowest layer. We have control of the ESXi. In GCE, we have no control over ESXi. I would look for other solutions. IBM Cloud Private does monitor the environment. They just give you a set of provisions from their portal. I use IBM Cloud Private due to this compliance reason. But it makes no difference because I need to build all these BPCs and subscribe to all these links to connect. If I host it within, I think it's a lot simpler. I rate IBM Cloud Private a five out of ten.
There are a couple of guidelines that I would suggest to consider when evaluating IBM Cloud Private. Firstly, it's important to determine your specific goals. If you're looking to establish a microservices-based architecture, there are alternative options in the market that might be more cost-effective. Secondly, ease of use is a crucial factor. There are other solutions on the market, such as VMware Tanzu, that provide additional benefits, including a reporting system, alarms, and monitoring tools under the same license, making it more operationally efficient. It should be noted that IBM has reportedly stopped selling it in certain regions, so I would suggest paying attention to that as well. Furthermore, the flexibility of buying individual software components independently may be more attractive than being tied to the bundled offerings in ICP. Lastly, if cost is a concern, open-source solutions like plain Kubernetes (K8s) offer more budget-friendly alternatives. You can select the features and licenses that fit your financial constraints. Overall, I would rate IBM Cloud Private a six out of ten because of performance concerns. It struggled when subjected to high traffic loads, and troubleshooting was challenging.
The solution is not at the same level as AWS or Azure but it is a good IBM product. I rate the solution an eight out of ten.
I think this IBM solution is the best for the industry because they support legacy systems, and since we're dealing with regulations, it's the best way for us to stay safe. The stability of the system is more important than anything. From a financial point of view, I recommend it. I rate the solution seven out of 10.