We performed a comparison between StreamSets and webMethods.io Integration based on real PeerSpot user reviews.
Find out in this report how the two Cloud Data Integration solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."It is really easy to set up and the interface is easy to use."
"The best feature that I really like is the integration."
"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."
"The entire user interface is very simple and the simplicity of creating pipelines is something that I like very much about it. The design experience is very smooth."
"In StreamSets, everything is in one place."
"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."
"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."
"The UI is user-friendly, it doesn't require any technical know-how and we can navigate to social media or use it more easily."
"The connectivity that the tool provides, along with the functionalities needed for our company's business, are some of the beneficial aspects of the product."
"Our use case is for integration factory for SAP. It is mostly for SAP integration."
"Oracle's self-service capabilities, of which we make extensive use, is the most valuable feature."
"There's hardware, software and application integration, providing hosting flexibility."
"I like the tool's scalability."
"It's easy to construct new interfaces like apps and client portals."
"The solution is scalable."
"The documentation is inadequate and has room for improvement because the technical support does not regularly update their documentation or the knowledge base."
"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."
"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."
"If you use JDBC Lookup, for example, it generally takes a long time to process data."
"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."
"The design experience is the bane of our existence because their documentation is not the best. Even when they update their software, they don't publish the best information on how to update and change your pipeline configuration to make it conform to current best practices. We don't pay for the added support. We use the "freeware version." The user community, as well as the documentation they provide for the standard user, are difficult, at best."
"The data collector in StreamSets has to be designed properly. For example, a simple database configuration with MySQL DB requires the MySQL Connector to be installed."
"One area for improvement could be the cloud storage server speed, as we have faced some latency issues here and there."
"I am not satisfied with the solution because it takes too much effort to migrate and add new information. The migration could be easier."
"Rules engine processes and BPM processes should be improved."
"The solution's release management feature could be better."
"The product's stability is an area of concern where improvements are required."
"webMethods.io Integration's installation is complex. It should also improve integration and connectors."
"It is difficult to maintain."
"The products, at the moment, are new and there should perhaps be support for the older version of the protocols."
StreamSets is ranked 8th in Data Integration with 24 reviews while webMethods.io Integration is ranked 22nd in Cloud Data Integration with 7 reviews. StreamSets is rated 8.4, while webMethods.io Integration is rated 7.8. The top reviewer of StreamSets writes "We no longer need to hire highly skilled data engineers to create and monitor data pipelines". On the other hand, the top reviewer of webMethods.io Integration writes "Though the tool provides great connectivity functionality, it needs to be made more stable". StreamSets is most compared with Fivetran, Azure Data Factory, Informatica PowerCenter, SSIS and Confluent, whereas webMethods.io Integration is most compared with webMethods Integration Server, SAP Cloud Platform, Apigee, Microsoft Azure API Management and Mule Anypoint Platform. See our StreamSets vs. webMethods.io Integration report.
See our list of best Cloud Data Integration vendors.
We monitor all Cloud Data Integration reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
