We performed a comparison between Denodo and StreamSets 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 can support a number of data sources, and it can pull flat files, from cloud-based databases or from those on-premises. Denodo can pull from any data source and interface with the view. Then, we can publish the view."
"The ability to transfer data is very valuable."
"In PL/SQL, first you need to gather all the data and then start writing the file, but in Denodo you fetch the data and write the data simultaneously. So, for example, if you have 1 million or 2 million records, you don't have to wait to fetch all of the 2 million; you can keep on fetching and writing in the file simultaneously."
"Denodo's best features are its performance, easy data transformation, and the job scheduler."
"The most valuable aspects of this solution are the short time frame in which you can deliver and connect."
"The performance and the speed to market are the most valuable features of this solution."
"Denodo makes it easy to export data as a service or data link to other services."
"This solution provides us with the ability to sync data, and make it available for anyone to use across the business."
"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."
"The most valuable feature is the pipelines because they enable us to pull in and push out data from different sources and to manipulate and clean things up within them."
"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"
"It's very easy to integrate. It integrates with Snowflake, AWS, Google Cloud, and Azure. It's very helpful for DevOps, DataOps, and data engineering because it provides a comprehensive solution, and it's not complicated."
"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."
"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."
"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."
"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 feature that you have to connect on LDAP needs improvement."
"The support is not the best and should be improved."
"The git configuration really should be improved."
"Denodo's training documentation could be improved by providing more material. From an administrative standpoint, I've found that only Denodo websites provide the usual tutorials. It may be because it's a bit of a restricted tool, but it results in trouble with learning. Normally, I can find help and solutions from other sources, but I haven't been able to find any for Denodo. Other that, it's fine and it performs well. I only have six months of experience, so I can't accurately suggest improvements."
"Denodo can improve usage management-related aspects. If you deal with the mini views, it gets stuck. The performance is very slow when we go with a large number of views and high volume."
"Performance management could be improved."
"It would be good if the solution provided a much-needed cellular platform."
"I would like to see a proper way to avoid killing the sourcing systems."
"We've seen a couple of cases where it appears to have a memory leak or a similar problem."
"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."
"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."
"The documentation is inadequate and has room for improvement because the technical support does not regularly update their documentation or the knowledge base."
"The software is very good overall. Areas for improvement are the error logging and the version history. I would like to see better, more detailed error logging information."
"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."
"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."
"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."
Denodo is ranked 12th in Data Integration with 29 reviews while StreamSets is ranked 8th in Data Integration with 24 reviews. Denodo is rated 7.8, while StreamSets is rated 8.4. The top reviewer of Denodo writes "Saves our underwriters' time with data virtualization, but could provide more learning resources". On the other hand, the top reviewer of StreamSets writes "We no longer need to hire highly skilled data engineers to create and monitor data pipelines". Denodo is most compared with Azure Data Factory, AWS Glue, Delphix, Mule Anypoint Platform and Informatica PowerCenter, whereas StreamSets is most compared with Fivetran, Azure Data Factory, Informatica PowerCenter, SSIS and IBM InfoSphere DataStage. See our Denodo vs. StreamSets report.
See our list of best Data Integration vendors and best Cloud 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.