We performed a comparison between StreamSets and TIBCO BusinessWorks based on real PeerSpot user reviews.
Find out in this report how the two Data Integration solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."It is a very powerful, modern data analytics solution, in which you can integrate a large volume of data from different sources. It integrates all of the data and you can design, create, and monitor pipelines according to your requirements. It is an all-in-one day data ops solution."
"The best feature that I really like is the integration."
"StreamSets’ data drift resilience has reduced the time it takes us to fix data drift breakages. For example, in our previous Hadoop scenario, when we were creating the Sqoop-based processes to move data from source to destinations, we were getting the job done. That took approximately an hour to an hour and a half when we did it with Hadoop. However, with the StreamSets, since it works on a data collector-based mechanism, it completes the same process in 15 minutes of time. Therefore, it has saved us around 45 minutes per data pipeline or table that we migrate. Thus, it reduced the data transfer, including the drift part, by 45 minutes."
"The most valuable features are the option of integration with a variety of protocols, languages, and origins."
"I have used Data Collector, Transformer, and Control Hub products from StreamSets. What I really like about these products is that they're very user-friendly. People who are not from a technological or core development background find it easy to get started and build data pipelines and connect to the databases. They would be comfortable like any technical person within a couple of weeks."
"The Ease of configuration for pipes is amazing. It has a lot of connectors. Mainly, we can do everything with the data in the pipe. I really like the graphical interface too"
"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."
"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 most valuable feature is the integration."
"The most valuable features are the stability and the time to market."
"The high availability, tolerance, and load balancing features are top-notch. Its scalability features are also pretty cool."
"XML to JSON transformations, out-of-the-box, helps to build REST services."
"The Business Studio interface based on SCA Standards helps to show the business logic at first look and improve code maintenance."
"One of the most valuable features is data transformation. We have some legacy systems which are in old technology, like SOAP, whereas the new ones are in REST. So we use BusinessWorks to transform data from one format to another, from SOAP to REST."
"The OSGI console is available to debug different issues and get low level informations on the applications development, like bundle, dependencies, etc."
"The most valuable feature is the low-code platform."
"Currently, we can only use the query to read data from SAP HANA. What we would like to see, as soon as possible, is the ability to read from multiple tables from SAP HANA. That would be a really good thing that we could use immediately. For example, if you have 100 tables in SQL Server or Oracle, then you could just point it to the schema or the 100 tables and ingestion information. However, you can't do that in SAP HANA since StreamSets currently is lacking in this. They do not have a multi-table feature for SAP HANA. Therefore, a multi-table origin for SAP HANA would be helpful."
"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."
"Sometimes, it is not clear at first how to set up nodes. A site with an explanation of how each node works would be very helpful."
"Using ETL pipelines is a bit complicated and requires some technical aid."
"We've seen a couple of cases where it appears to have a memory leak or a similar problem."
"The execution engine could be improved. When I was at their session, they were using some obscure platform to run. There is a controller, which controls what happens on that, but you should be able to easily do this at any of the cloud services, such as Google Cloud. You shouldn't have any issues in terms of how to run it with their online development platform or design platform, basically their execution engine. There are issues with that."
"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."
"There are not many plugins available to integrate the databases. We have to write it in Java and integrate it. The developers should have more knowledge. These are the three main aspects that they could improve."
"The communication protocols could be improved."
"Technical support is average. It's not the best."
"The cost has room for improvement."
"This solution's cloud could be improved. I don't know whether it was because we didn't have the internal expertise or if it was the product itself, but since they came later—I think only two or three years into the cloud—after many other iPaaS that had been in the cloud for longer, I feel that maybe they haven't matured in terms of the cloud."
"Cloud fitness is lacking"
"They don't support out of the box - you have to buy adapters or you have to have the technology."
"Improve Business Studio's stability to further minimize development time."
StreamSets is ranked 8th in Data Integration with 24 reviews while TIBCO BusinessWorks is ranked 18th in Data Integration with 23 reviews. StreamSets is rated 8.4, while TIBCO BusinessWorks is rated 8.0. 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 TIBCO BusinessWorks writes "Reliable integration solution with robust communication capabilities and good scalability". StreamSets is most compared with Fivetran, Azure Data Factory, Informatica PowerCenter, SSIS and Oracle GoldenGate, whereas TIBCO BusinessWorks is most compared with webMethods Integration Server, Mule Anypoint Platform, Spring Cloud Data Flow, Talend Open Studio and Confluent. See our StreamSets vs. TIBCO BusinessWorks report.
See our list of best Data Integration vendors.
We monitor all 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.
