IBM Cloud Pak for Integration Reviews

The use cases involve connecting and converting data from one system to another, often involving alterations in the data's format or structure.

The most preferable aspect would be the elimination of the command, which was a significant improvement. In the past, it was a challenge, but now we can proceed smoothly with the implementation of our policies and everything is managed through JCP. It's still among the positive aspects, and it's a valuable feature.

The pricing can be improved. 

I have been using IBM Cloud Pak for Integration for the past three years.

It is stable.

It is scalable and I haven't encountered any problems. The data handled itself automatically without any issues.

In the beginning, when we were implementing new tools and meticulously scrutinizing every detail, we faced uncertainty in establishing a connection with SAP while operating on Windows 10. However, with time, we managed to successfully address all the challenges. We received valuable insights from our research efforts, and when we initially started, the situation was quite novel. Over time, through our continuous efforts, we achieved the connection, but there were some lingering issues that they also couldn't resolve, even though they were diligently investigating the matter. In the end, we were able to find a solution ourselves.

Positive

I was dealing with an older version of IIB, and migrating to version 54 was a significant shift. It presented some challenges, but it proved to be a valuable learning experience. It is deployed both on the cloud and on premises.

It is an expensive solution. 

Previously, it was coded in IID, an older version of Cloudpath. Migrating everything to Cloudpath would have been a simpler task. Additionally, the speed and precision of data processing and integrations were significantly faster in comparison to the new setup.

I recommend using it because, in today's context, the cloud plays a significant role. Within the same user interface, you can develop applications and manage multiple applications, making it a more user-friendly option. Moreover, you can explore various other technologies while deploying on the cloud, broadening your knowledge of cloud technologies. In my case, the transition led to my learning of Kubernetes, enabling multi-scaling and expanding my technical skills. It was a valuable experience, and I had the opportunity to learn many new things during the migration process.

I can easily rate it an eight or nine out of ten.

It manages APIs and integrates microservices at the enterprise level. It offers a range of capabilities for handling APIs, microservices, and various integration needs. The platform supports thousands of APIs, providing tools for building, managing, and securing them effectively.

Redirection is a key feature. It helps in managing multiple microservices by centralizing control and access. With Monalytics, microservices are separated, and redirection ensures they are efficiently managed, including load balancing and recovery.

Enterprise bots are needed to balance products like Kafka and Confluent.

I have been using IBM Cloud Pak for Integration for two years.

Spring Framework is known for its simplicity and ease of use. For instance, IBM Cloud Pak for Integration leverages Spring Boot and Spring Cloud technologies. It also features its own API tools, which are straightforward to use. IBM also works extensively with various services and traditional architectures, continuously evolving to manage complexity over time.

The initial setup is straightforward. Two people are required for it.

IBM is already priced.

I rate the product’s pricing an eight out of ten, where one is cheap, and ten is expensive.

IBM Cloud Pak for Integration includes monitoring capabilities to track the performance and health of your integrations. You can quickly roll back to a previous version if an issue arises. Additionally, it supports incremental deployments, allowing you to shift traffic to a new version of an API gradually. For example, you can start by directing 10% of traffic to the new version while the rest continue using the legacy version. If everything works as expected, you can gradually increase the traffic to the new version over time.

IBM Cloud Pak for Integration has a client base that includes numerous organizations using AI and machine learning technologies. We leverage an open-source machine learning framework and integrate it with Kafka to help create and manage various products and data retrieval processes.

For companies with private data, the framework first retrieves relevant data from a GitHub database, which is then combined with the final request before being sent to a language model like GPT. This ensures that the language model uses your specific data to generate responses.

Kafka plays a key role by streaming real-time data from file systems and databases like Oracle and Microsoft SQL. This data is published to Kafka topics, then vectorized and used with artificial intelligence to enhance the overall process. It's like an old-fashioned approach. The best way is to redesign it with products such as Kafka.

Overall, I rate the solution an eight out of ten.

We use the solution for API integrations for various sectors, including travel, banking, etc.

The solution's most valuable feature is streaming.

The solution's streaming feature needs more enhancement for multiple integrations. Also, queuing and messaging features need improvement as well. In addition, they should integrate it with monitoring software for better analysis.

I have been using the solution for fifteen months.

It is a stable solution.

It is a scalable solution.

The solution's initial setup process is easy.

The solution's pricing model is very flexible. We can tailor it depending on budget and requirements. On average, it costs around $3000-$4000 per year.

I rate the solution an eight out of ten.

We've been using Cloud Pak since it was launched. That was around one year ago. We've been working with IBM since 1995, so we have a long history with the company. After the Red Hat acquisition, IBM renamed every single product. The company is very quick about renaming products.

Cloud Pak is stable. It is stable after it has been rolled out and tested. 

Cloud Pak for Integration is definitely scalable. That is the most important criteria. 

Setting up Cloud Pak for Integration is relatively complex. It's not as easy because it has not yet been fully integrated. You still have some products that are still not containerized, so you still have to run them on a dedicated VM. 

I think a large organization will get a return from Cloud Pak, but it might not bring an ROI for a smaller enterprise.

I rate Cloud Pak for Integration eight out of 10. It requires a particular high-profile skillset, and it's not easy to implement. It is definitely stable and scalable, but it needs expertise.

We use the solution for our clients. We primarily use the solution for multi-cloud management or automation. It's largely for integration. Automation is another one that we use. 

The solution helps you to do an integration between core systems. Basically, it gives you a foundation for some products - especially container platforms and integration platforms like IBM, Kafka, or DataPower, such as IP management. It is like a bundle of other products. You can use it based on how much licensing you have and it is deployed on a lot of capacities or integrations that you can use.

The most valuable aspect of the Cloud Pak, in general, is the flexibility that you have to use the product.

If you need something to do with integration and enterprise especially, this product will help you.

The product has the capacity to do file processing automation and accounting. The flexibility that they give you to use it is very, very interesting. 

The product includes the OpenShift Container Platform. Therefore, it's very practical as you don't have to license extra on that part and you don't really have to deal with the foundation for the OpenShift Cloud platform. You can do whatever you need to on the container side.

In general, the solution works very, very well.

The stability is very good.

What needs to be improved is the restriction that they have on the product. With this solution, you can deploy all the IBM products that are included in the Cloud Pak over the OpenShift but you cannot deploy anything else. That can be limiting. 

The initial setup is not easy.

We've used the solution for about three years or so. It's a recent addition.

The solution is very stable. There are no bugs or glitches. It does not crash or freeze. It's reliable.

The initial setup is quite difficult. It's not easy, however, it's not meant to be easy. It's really complicated as it's a million moving parts of software and solution. That said, it is expected. 

How long it takes to deploy, depends on if you would like to deploy everything and configure everything or if you are doing something more limited. It could take you two or three weeks.

We are an IBM partner.

It's something that we use for our clients especially. We're specialized in the product, and it's something that we have really good experience with. It's multi-cloud. You can have it on-premise or any other kind of cloud.

We use both the 2020 and 2021 versions of the solution.

I'd rate the solution at a nine out of ten. We've mostly been quite satisfied with the product in general.