We performed a comparison between FME 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."All spatial features are unrivaled, and the possibility to execute them based on a scheduled trigger, manual, e-mail, Websocket, tweet, file/directory change or virtually any trigger is most valuable."
"We make minor subtle changes to the workbenches to improve it. We can share the workbenches. We don't have to use GitHub or anything else."
"It has standard plug-ins available for different data sources."
"It has a very friendly user interface. You don't need to use a lot of code. For us that's the most important aspect about it. Also, it has a lot of connectors and few forms. It has a strong facial aspect. It can do a lot of facial analysis."
"The most valuable feature of FME is the graphical user interface. There is nothing better. It is very easy to debug because you can see all steps where there are failures. Overall the software is easy to optimize a process."
"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 ability to have a good bifurcation rate and fewer mistakes is valuable."
"The most valuable features are the option of integration with a variety of protocols, languages, and origins."
"In StreamSets, everything is in one place."
"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."
"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 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 really easy to set up and the interface is easy to use."
"Improvements could be made to mapping presentations."
"FME can improve the geographical transformation. I've had some problems with the geographical transformations, but it's probably mostly because I'm not the most skilled geographer in-house. The solution requires some in-depth knowledge to perform some functions."
"FME's price needs improvement for the African market."
"The one thing that always appears in the community is the ability to make really easy loops to loop through data efficiently. That needs to be added at some point."
"To get a higher rating, it would have to improve the price and the associated scalability. These are the main issues."
"Sometimes, when we have large amounts of data that is very efficiently stored in Hadoop or Kafka, it is not very efficient to run it through StreamSets, due to the lack of efficiency or the resources that StreamSets is using."
"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 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."
"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 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."
"There aren't enough hands-on labs, and debugging is also an issue because it takes a lot of time. Logs are not that clear when you are debugging, and you can only select a single source for a pipeline."
"We often faced problems, especially with SAP ERP. We struggled because many columns weren't integers or primary keys, which StreamSets couldn't handle. We had to restructure our data tables, which was painful. Also, pipeline failures were common, and data drifting wasn't addressed, which made things worse. Licensing was another issue we encountered."
"If you use JDBC Lookup, for example, it generally takes a long time to process data."
FME is ranked 24th in Data Integration with 5 reviews while StreamSets is ranked 8th in Data Integration with 24 reviews. FME is rated 8.6, while StreamSets is rated 8.4. The top reviewer of FME writes "Great for handling large volumes of data, but it is priced a bit high". 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". FME is most compared with Azure Data Factory, Alteryx Designer, Talend Open Studio, SSIS and Informatica PowerCenter, whereas StreamSets is most compared with Fivetran, Azure Data Factory, Informatica PowerCenter, SSIS and IBM InfoSphere DataStage. See our FME vs. StreamSets 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.