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

StreamSets vs WSO2 Enterprise Integrator comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 19, 2024

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

StreamSets
Ranking in Data Integration
24th
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
21
Ranking in other categories
No ranking in other categories
WSO2 Enterprise Integrator
Ranking in Data Integration
28th
Average Rating
7.6
Reviews Sentiment
6.8
Number of Reviews
20
Ranking in other categories
Enterprise Service Bus (ESB) (7th)
 

Mindshare comparison

As of September 2026, in the Data Integration category, the mindshare of StreamSets is 1.1%, down from 1.4% compared to the previous year. The mindshare of WSO2 Enterprise Integrator is 1.0%, up from 0.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Data Integration Mindshare Distribution
ProductMindshare (%)
StreamSets1.1%
WSO2 Enterprise Integrator1.0%
Other97.9%
Data Integration
 

Featured Reviews

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.
AC
Technical director at Cremete
Effective data transformation and integration in complex environments with high functionality
Something that could be improved in WSO2 Enterprise Integrator is that the problem is not a lack of capability or functionalities. The problem is that it is a very complex environment. To put your hand on this environment is a very demanding task. This is the real problem. The problem is not about the product, but about the complexity to manage, to configure, to decide what to do. I have some experience using SAP R/3. It seems to me something similar. When you have to configure a situation with a client, especially for a client not in an industrial sector, but in a service sector, it is quite usual that you are in trouble for some reason. This is always the story that I found in the implementations I have done. Maybe there are only three or four big problems, in some other cases there are more than that, but this is the situation usually. For WSO2 Enterprise Integrator, not the same, but I must say it is quite often there is a need to put together some pieces and make it work in a coordinated way.

Quotes from Members

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

Pros

"For me, the most valuable features in StreamSets have to be the Data Collector and Control Hub, but especially the Data Collector. That feature is very elegant and seamlessly works with numerous source systems."
"It is really easy to set up and the interface is easy to use."
"StreamSets' reusable assets have helped to reduce workload by 32% to 40%."
"In StreamSets, everything is in one place."
"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."
"I really appreciate the numerous ready connectors available on both the source and target sides, the support for various media file formats, and the ease of configuring and managing pipelines centrally."
"Also, the intuitive canvas for designing all the streams in the pipeline, along with the simplicity of the entire product are very big pluses for me. The software is very simple and straightforward. That is something that is needed right now."
"The ETL capabilities are very useful for us. We extract and transform data from multiple data sources, into a single, consistent data store, and then we put it in our systems. We typically use it to connect our Apache Kafka with data lakes. That process is smooth and saves us a lot of time in our production systems."
"It has improved our time management because development is quicker."
"The stability is excellent."
"The solution basically conforms to our standards."
"In my opinion, the most valuable aspect of this solution is its extensive range of adaptors and connectors. This feature holds significant importance and provides great value to users."
"From the capabilities and functional possibility and anything else technical, it is a very well-done product, I have to say."
"Currently, I find the configuration part quite valuable, where you can easily configure things."
"The drag-and-drop features for connectors are very valuable."
"The solution has two main parts: integration and transformation. It's very user-friendly and easy to understand for everyone."
 

Cons

"They need to improve their customer care services. Sometimes it has taken more than 48 hours to resolve an issue. That should be reduced. They are aware of small or generic issues, but not the more technical or deep issues. For those, they require some time, generally 48 to 72 hours to respond. That should be improved."
"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 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."
"Visualization and monitoring need to be improved and refined."
"We create pipelines or jobs in StreamSets Control Hub. It is a great feature, but if there is a way to have a folder structure or organize the pipelines and jobs in Control Hub, it would be great. I submitted a ticket for this some time back."
"The logging mechanism could be improved. If I am working on a pipeline, then create a job out of it and it is running, it will generate constant logs. So, the logging mechanism could be simplified. Now, it is a bit difficult to understand and filter the logs. It takes some time."
"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."
"If I have to buy software, then it becomes expensive for me."
"The scalability is not strong. If you want to scale it you have to install multiple servers."
"In my opinion, the administration model and interface, of Carbon, are lacking in terms of its features and user experience."
"The server is very specific and it is very difficult to get experience with it."
"For simpler tasks or simpler use cases, we avoid using WSO2 Enterprise Integrator because it is quite complex."
"One of the reasons that we are looking for a replacement is their way of defining integration. The language of the XML structures that I use to describe the integrations are not that standard, and it's not easy to find people who are familiar with this approach."
"We had some challenges with the installation of this solution."
"The configuration of the product is not an easy task for everyone."
 

Pricing and Cost Advice

"The pricing is too fixed. It should be based on how much data you need to process. Some businesses are not so big that they process a lot of data."
"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."
"I believe the pricing is not equitable."
"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."
"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."
"The pricing is affordable for any business."
"Its pricing is pretty much up to the mark. For smaller enterprises, it could be a big price to pay at the initial stage of operations, but the moment you have the Seed B or Seed C funding and you want to scale up your operations and aren't much worried about the funds, at that point in time, you would need a solution that could be scaled."
"I rate the product price a six on a scale of one to ten, where one is low price and ten is high price."
"The pricing of WSO2 Enterprise Integrator for enterprise subscriptions can be considered expensive, especially from the perspective of someone who prefers open-source software."
"The open-source, unsupported version is available free of charge."
"The solution costs about 20,000 or 30,000 euros per year, per instance."
"It is a low-cost solution."
"The cost is better than IBM Cloud Pak."
report
Use our free recommendation engine to learn which Data Integration solutions are best for your needs.
913,806 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
10%
Outsourcing Company
9%
Comms Service Provider
7%
Healthcare Company
6%
Outsourcing Company
14%
Financial Services Firm
10%
Construction Company
8%
Comms Service Provider
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise2
Large Enterprise11
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise2
Large Enterprise11
 

Questions from the Community

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.
What needs improvement with WSO2 Enterprise Integrator?
Something that could be improved in WSO2 Enterprise Integrator is that the problem is not a lack of capability or functionalities. The problem is that it is a very complex environment. To put your ...
What is your primary use case for WSO2 Enterprise Integrator?
A typical use case for WSO2 Enterprise Integrator is when I am in an interoperability environment with healthcare facilities and I have to put together a lot of applications that share some HL7 mes...
What advice do you have for others considering WSO2 Enterprise Integrator?
For simpler tasks or simpler use cases, we avoid using WSO2 Enterprise Integrator because it is quite complex. So it is easier to manage some more simple solutions than that. WSO2 Enterprise Integr...
 

Overview

 

Sample Customers

Availity, BT Group, Humana, Deluxe, GSK, RingCentral, IBM, Shell, SamTrans, State of Ohio, TalentFulfilled, TechBridge
West
Find out what your peers are saying about StreamSets vs. WSO2 Enterprise Integrator and other solutions. Updated: September 2026.
913,806 professionals have used our research since 2012.