No more typing reviews! Try our Samantha, our new voice AI agent.

IBM Cloud Pak for Integration vs StreamSets comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

IBM Cloud Pak for Integration
Average Rating
8.6
Reviews Sentiment
7.0
Number of Reviews
5
Ranking in other categories
API Management (29th), Cloud Data Integration (20th)
StreamSets
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
21
Ranking in other categories
Data Integration (24th)
 

Featured Reviews

Igor Khalitov - PeerSpot reviewer
Owner/Full Stack Software Engineer at Maraphonic, Inc.
Manages APIs and integrates microservices with redirection feature
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.
SS
Enterprise Solutions Architect at a energy/utilities company with 1,001-5,000 employees
Enables effective batch loading with visual interface and enterprise support
One issue I observed with StreamSets is that the memory runs out quickly when processing large volumes of data. Because of this memory issue, we have to upgrade our EC2 boxes in the Amazon AWS infrastructure. I had to switch to a new EC2 box, even though the processor was not fully utilized. It would be beneficial if StreamSets addressed any potential memory leak issues to prevent unnecessary upgrades. Additionally, it would be a great enhancement if StreamSets could produce a lineage graph to visualize how the data has passed through the system.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Redirection is a key feature. It helps in managing multiple microservices by centralizing control and access."
"It is a stable solution."
"In general, the solution works very, very well."
"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 most valuable aspect of the Cloud Pak, in general, is the flexibility that you have to use the product."
"Cloud Pak for Integration is definitely scalable. That is the most important criteria."
"One of the things I like is the data pipelines. They have a very good design. Implementing pipelines is very straightforward. It doesn't require any technical skill."
"What I love the most is that StreamSets is very light. It's a containerized application. It's easy to use with Docker. If you are a large organization, it's very easy to use Kubernetes."
"This product was a lot easier to use than the one we had before it, and it took us half an hour and we were set up and running it the first time."
"It is really easy to set up and the interface is easy to use."
"StreamSets data drift feature gives us an alert upfront so we know that the data can be ingested. Whatever the schema or data type changes, it lands automatically into the data lake without any intervention from us, but then that information is crucial to fix for downstream pipelines, which process the data into models, like Tableau and Power BI models. This is actually very useful for us. We are already seeing benefits. Our pipelines used to break when there were data drift changes, then we needed to spend about a week fixing it. Right now, we are saving one to two weeks. Though, it depends on the complexity of the pipeline, we are definitely seeing a lot of time being saved."
"In StreamSets, everything is in one place."
"StreamSets has definitely helped us in getting the information into our data lake very quickly, in terms of ingestion, and the most important thing is it has helped us from a resourcing point of view because you can easily upskill a BI or ETL resource without any programming knowledge to work with this, which has drastically reduced the time that we are spending on workloads by 60% to 70% as well as reducing the time spent on ingestion by 30%."
"The most valuable would be the GUI platform that I saw. I first saw it at a special session that StreamSets provided towards the end of the summer. I saw the way you set it up and how you have different processes going on with your data. The design experience seemed to be pretty straightforward to me in terms of how you drag and drop these nodes and connect them with arrows."
 

Cons

"The pricing can be improved."
"The initial setup is not easy."
"What needs to be improved is the restriction that they have on the product."
"Enterprise bots are needed to balance products like Kafka and Confluent."
"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."
"Its queuing and messaging features need improvement."
"The documentation is inadequate and has room for improvement because the technical support does not regularly update their documentation or the knowledge base."
"The monitoring visualization is not that user-friendly. It should include other features to visualize things, like how many records were streamed from a source to a destination on a particular date."
"One issue I observed with StreamSets is that the memory runs out quickly when processing large volumes of data. Because of this memory issue, we have to upgrade our EC2 boxes in the Amazon AWS infrastructure."
"There are a few things that can be better."
"In terms of the product, I don't think there is any room for improvement because it is very good. One small area of improvement that is very much needed is on the knowledge base side. Sometimes, it is not very clear how to set up a certain process or a certain node for a person who's using the platform for the first time."
"If you use JDBC Lookup, for example, it generally takes a long time to process data."
"One area for improvement could be the cloud storage server speed, as we have faced some latency issues here and there."
"StreamSets should provide a mechanism to be able to perform data quality assessment when the data is being moved from one source to the target."
 

Pricing and Cost Advice

"It is an expensive solution."
"The solution's pricing model is very flexible."
"StreamSets Data Collector is open source. One can utilize the StreamSets Data Collector, but the Control Hub is the main repository where all the jobs are present. Everything happens in Control Hub."
"StreamSets is an expensive solution."
"There are different versions of the product. One is the corporate license version, and the other one is the open-source or free version. I have been using the corporate license version, but they have recently launched a new open-source version so that anybody can create an account and use it. The licensing cost varies from customer to customer. I don't have a lot of input on that. It is taken care of by PMO, and they seem fine with its pricing model. It is being used enterprise-wide. They seem to have got a good deal for StreamSets."
"I believe the pricing is not equitable."
"The overall cost is very flexible so it is not a burden for our organization... However, the cost should be improved. For small and mid-size organizations it might be a challenge."
"It's not so favorable for small companies."
"The licensing is expensive, and there are other costs involved too. I know from using the software that you have to buy new features whenever there are new updates, which I don't really like. But initially, it was very good."
"We use the free version. It's great for a public, free release. Our stance is that the paid support model is too expensive to get into. They should honestly reevaluate that."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
909,948 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
13%
Manufacturing Company
12%
Construction Company
9%
Government
8%
Financial Services Firm
12%
Comms Service Provider
7%
Manufacturing Company
6%
Outsourcing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise2
Large Enterprise11
 

Questions from the Community

What needs improvement with IBM Cloud Pak for Integration?
Enterprise bots are needed to balance products like Kafka and Confluent.
What is your primary use case for IBM Cloud Pak for Integration?
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 thousa...
What advice do you have for others considering IBM Cloud Pak for Integration?
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. Addition...
What needs improvement with StreamSets?
One issue I observed with StreamSets is that the memory runs out quickly when processing large volumes of data. Because of this memory issue, we have to upgrade our EC2 boxes in the Amazon AWS infr...
What is your primary use case for StreamSets?
We are using StreamSets for batch loading.
What advice do you have for others considering StreamSets?
If asked, I definitely recommend StreamSets to other users. My overall rating for the solution is nine.
 

Overview

 

Sample Customers

CVS Health Corporation
Availity, BT Group, Humana, Deluxe, GSK, RingCentral, IBM, Shell, SamTrans, State of Ohio, TalentFulfilled, TechBridge
Find out what your peers are saying about Amazon Web Services (AWS), Informatica, Palantir and others in Cloud Data Integration. Updated: August 2026.
909,948 professionals have used our research since 2012.