IBM Cloud Pak for Integration
Unified, Cloud-Native Integration Platform on OpenShift That Simplifies Architecture
I also appreciate the cloud-native approach. Everything is deployed as Kubernetes operators, making it easier to automate installations, upgrades, and configuration using GitOps and CI/CD pipelines. Once the platform is established, new environments can be deployed in a repeatable and consistent manner.
Another strength is the integration between the products. APIs exposed through API Connect can easily integrate with App Connect flows, IBM MQ messaging, Kafka events, and DataPower security policies, all within the same ecosystem. This significantly reduces integration effort compared to stitching together multiple vendors' products.
One of the major advantages of IBM Cloud Pak for Integration is its flexible licensing model. A Cloud Pak for Integration (CP4I) license is not tied to a single product. Instead, the available Virtual Processor Core (VPC) entitlement can be allocated to any of the supported components, such as IBM API Connect, App Connect, IBM MQ, Event Streams, DataPower Gateway, Aspera, or other eligible capabilities.
The platform is also resource-intensive. For development or proof-of-concept environments, the infrastructure requirements can be significant, although this is understandable given the number of enterprise services that are included.
While IBM's documentation is comprehensive, it can sometimes be difficult to find practical end-to-end deployment examples, especially for GitOps, automation, disaster recovery, and upgrade scenarios. More production-focused examples would help organizations adopt the platform more quickly.
Manages APIs and integrates microservices with redirection feature
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
Enterprise bots are needed to balance products like Kafka and Confluent.
For how long have I used the solution?
I have been using IBM Cloud Pak for Integration for two years.
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
The initial setup is straightforward. Two people are required for it.
What's my experience with pricing, setup cost, and licensing?
IBM is already priced.
I rate the product’s pricing an eight out of ten, where one is cheap, and ten is expensive.
What other advice do I have?
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.
Review for IBM cloud PAK: befitting tool
High-performance data transport, enhanced data autonomy
easy for begineers also
IBM pak tool for data analysis
My Experience with IBM Cloud Pak for Integration : Ups & Downs
User-Friendly : Although it look's complex in starting, but after a time interface feels quite intutive and navigating through platform is quite straightforward and anticipated.
API : Last but not the least it's API management tools are top-notch. Creating and managing APIs for me has really become hassel free now.
Resources : It requires a decent amount of resources. Small business or business not equiped with a decent infrastructure, might find it bit sluggish.
Documentation : A lot of documentation, which is a good part but in daily work life sometimes it feels like finding a needle in haystack.
ETL : It's ETL capibilities are again top-notch with real time data integration and also handling a huge amount of data is now so easy.
Great to work in IBM cloud
My Experience with IBM Cloud Pak
1. Its hastle free and easy to use than traditional integration tools.
2. UI and the transition/ working is really smooth.
3. Varies new features and customisable as well
2. Data visualisation and all features were also really helpful for me.
2. Its hastle free and easy to use than traditional integration tools.
IBM cloud park data system
Quick data transfer and reduced dependency on third party services
Also its not like we have to pay a standard amount to entire package some of which we don't need, we can actually pay only certain products that we need here hence its cost effective. Actually it's flexibility of private and public cloud enablement made it easier for the application deployment. Last but not least it's AI powered hence saves time.
Also CI CD should be enhanced
We can easily connect applications running in multiple clouds .
Api monitoring made easy. And better api flow readability.