Try our new research platform with insights from 80,000+ expert users

StreamSets vs webMethods.io 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:
 

ROI

Sentiment score
8.1
StreamSets speeds up data processing, boosts efficiency and revenue, simplifies tasks, enhances security, and reduces costs significantly.
Sentiment score
7.1
webMethods.io delivers rapid ROI through cost savings, reduced downtime, and increased productivity, depending on specific implementations.
 

Customer Service

Sentiment score
6.7
StreamSets support is responsive and knowledgeable, offering effective solutions, though response times and technical handling could improve.
Sentiment score
6.6
webMethods.io's customer service is praised for responsiveness, but users note occasional delays and desire improved technical support communication.
IBM technical support sometimes transfers tickets between different teams due to shift changes, which can be frustrating.
 

Scalability Issues

Sentiment score
7.6
StreamSets is scalable and flexible, favored for cloud use but could improve auto-scaling for large data migrations.
Sentiment score
7.2
webMethods.io is praised for its scalability in cloud and on-premises environments, with some licensing constraints noted.
Vertically, scalability is fine, however, I have not expanded horizontally with the product yet.
 

Stability Issues

Sentiment score
7.8
StreamSets is praised for stability and reliability, despite minor memory issues, with high user ratings and market competitiveness.
Sentiment score
7.6
webMethods.io is generally stable and reliable, with minor issues in specific modules and cloud version maturity needed.
There are some issues like the tool hanging or the need for additional jars when exposing web services.
 

Room For Improvement

StreamSets struggles with integration, real-time processing, clarity in UI, memory issues, security, documentation, and cloud storage performance.
webMethods.io needs clearer documentation, better scalability, intuitive interfaces, and improved integration and cost-effectiveness for enhanced user experience.
It would be beneficial if StreamSets addressed any potential memory leak issues to prevent unnecessary upgrades.
A special discount of at least 50% for old customers would allow us to expand our services and request more resources.
 

Setup Cost

StreamSets provides flexible pricing models, with varied user satisfaction, favoring larger enterprises over smaller companies due to cost.
Enterprise buyers find webMethods.io costly but valuable, offering flexibility and comprehensive solutions, particularly beneficial for large-scale enterprises.
 

Valuable Features

StreamSets offers intuitive interface, extensive connectors, and features accessible to non-technical users for seamless data integration and manipulation.
webMethods.io excels in seamless integration, user-friendliness, robust security, and scalability, offering efficient tools and reliable management for diverse needs.
It allows a hybrid installation approach, rather than being completely cloud-based or on-premises.
It facilitates the exposure of around 235 services through our platform to feed various government entities across the entire country.
 

Categories and Ranking

StreamSets
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
21
Ranking in other categories
Data Integration (15th)
webMethods.io
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
92
Ranking in other categories
Business-to-Business Middleware (3rd), Enterprise Service Bus (ESB) (3rd), Managed File Transfer (MFT) (10th), API Management (10th), Cloud Data Integration (7th), Integration Platform as a Service (iPaaS) (5th)
 

Featured Reviews

Karthik Rajamani - PeerSpot reviewer
Integrates with different enterprise systems and enables us to easily build data pipelines without knowing how to code
There are a few things that can be better. 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. There are certain features that are only available at certain stages. For example, HTTP Client has some great features when it is used as a processor, but those features are not available in HTTP Client as a destination. There could be some improvements on the group side. Currently, if I want to know which users are a part of certain groups, it is not straightforward to see. You have to go to each and every user and check the groups he or she is a part of. They could improve it in that direction. Currently, we have to put in a manual effort. In case something goes wrong, we have to go to each and every user account to check whether he or she is a part of a certain group or not.
Michele Illiano - PeerSpot reviewer
Can function as an ESB along with the core product, with decent integration of message protocols
I have noticed that webMethods ActiveTransfer has had problems when handling large files. For example, when we receive (and perform operations on) files that are larger than about 16 MB, the software starts losing performance. This is why, for most customers who have to deal with big files, I suggest that they use a product other than ActiveTransfer. I would like to note that this problem mainly concerns large files that undergo extra operations, such assigning, unassigning, or file translation. When these operations take place on large files, ActiveTransfer will use up a lot of resources. Within the product itself, I also believe that there is room for improvement in terms of optimization when it comes to general performance. I suspect that the issues underlying poor optimization are because it is all developed in Java. That is, all the objects and functions that are used need to be better organized, especially when it comes to big files but also overall. webMethods ActiveTransfer was born as an ESB to handle messages, and these messages were typically very short, i.e. small in size. A message is data that you have to send to an application, where it must be received in real-time and possibly processed or acknowledged elsewhere in the system as well. So, because it was initially designed for small messages, it struggles with performance when presented with very large files. All this to say, I suggest that they have an engineer reevaluate the architecture of the product in order to consider cases where large files are sent, and not only small ones. As for new features, compared to other products in the market, I think Software AG should be more up to date when it comes to extra protocol support, especially those protocols that other solutions have included in their products by default. Whenever we need to add an unsupported protocol, we have to go through the effort of custom development in order to work with it. Also, all the banks are obligated to migrate to the new standards, and big companies are all handling translations and operating their libraries with the new protocol formats. But webMethods ActiveTransfer doesn't seem to be keeping up with this evolution. Thus, they should aim to be more compliant in future, along the lines of their competitors such as IBM and Primeur.
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
848,989 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Computer Software Company
11%
Manufacturing Company
9%
Insurance Company
9%
Financial Services Firm
14%
Computer Software Company
13%
Manufacturing Company
12%
Retailer
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about StreamSets?
The best thing about StreamSets is its plugins, which are very useful and work well with almost every data source. It's also easy to use, especially if you're comfortable with SQL. You can customiz...
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 do you like most about Built.io Flow?
The tool helps us to streamline data integration. Its BPM is very strong and powerful. The solution helps us manage digital transformation.
What is your experience regarding pricing and costs for Built.io Flow?
webMethods.io is expensive. We have multiple components, and you need to pay for each of them.
What needs improvement with Built.io Flow?
webMethods.io needs to incorporate ChatGPT to enhance user experience. It can offer a customized user experience.
 

Comparisons

 

Also Known As

No data available
Built.io Flow, webMethods Integration Server, webMethods Trading Networks, webMethods ActiveTransfer, webMethods.io API
 

Overview

 

Sample Customers

Availity, BT Group, Humana, Deluxe, GSK, RingCentral, IBM, Shell, SamTrans, State of Ohio, TalentFulfilled, TechBridge
Cisco, Agralogics, Dreamforce, Cables & Sensors, Sacramento Kings
Find out what your peers are saying about StreamSets vs. webMethods.io and other solutions. Updated: April 2025.
848,989 professionals have used our research since 2012.