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

StreamSets vs WhereScape RED comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 19, 2024
 

Categories and Ranking

StreamSets
Ranking in Data Integration
9th
Average Rating
8.4
Reviews Sentiment
7.1
Number of Reviews
22
Ranking in other categories
No ranking in other categories
WhereScape RED
Ranking in Data Integration
46th
Average Rating
8.2
Reviews Sentiment
7.2
Number of Reviews
15
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of December 2024, in the Data Integration category, the mindshare of StreamSets is 1.8%, up from 1.4% compared to the previous year. The mindshare of WhereScape RED is 1.1%, up from 1.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Data Integration
 

Featured Reviews

Reyansh Kumar - PeerSpot reviewer
We no longer need to hire highly skilled data engineers to create and monitor data pipelines
The things I like about StreamSets are its * overall user interface * efficiency * product features, which are all good. Also, the scheduling within the data engineering pipeline is very much appreciated, and it has a wide range of connectors for connecting to any data sources like SQL Server, AWS, Azure, etc. We have used it with Kafka, Hadoop, and Azure Data Factory Datasets. Connecting to these systems with StreamSets is very easy. You just need to configure the data sources, the paths and their configurations, and you are ready to go. It is very efficient and very easy to use for ETL pipelines. It is a GUI-based interface in which you can easily create or design your own data pipelines with just a few clicks. As for moving data into modern analytics systems, we are using it with Microsoft Power BI, AWS, and some on-premises solutions, and it is very easy to get data from StreamSets into them. No hardcore coding or special technical expertise is required. It is also a no-code platform in which you can configure your data sources and data output for easy configuration of your data pipeline. This is a very important aspect because if a tool requires code development, we need to hire software developers to get the task done. By using StreamSets, it can be done with a few clicks.
reviewer1618884 - PeerSpot reviewer
Quick to set up, flexible, and stable
The scheduling part I don't like due to the fact that it allows you to schedule as a parent and child and other things, however, the error trackability has to be a little more user-friendly. It's also not user-friendly in the sense that it loads all the jobs and there are not enough filters so that it doesn't need to load everything. If the job fails, you don't get any type of alert or email. It would be ideal if there was some sort of automated alert message. Technical support isn't the best. It would be ideal if we understood how to do it in a card exception regarding exclusion, where the card is captured separately rather than filling the whole process on the data inbound side. Certain workloads like this are organized in such a way where you seem to be doubling the work as opposed to streamlining the process.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"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."
"The ability to have a good bifurcation rate and fewer mistakes is valuable."
"StreamSets data drift feature gives us an alert upfront so we know that the data can be ingested. Whatever the schema or data type changes, it lands automatically into the data lake without any intervention from us, but then that information is crucial to fix for downstream pipelines, which process the data into models, like Tableau and Power BI models. This is actually very useful for us. We are already seeing benefits. Our pipelines used to break when there were data drift changes, then we needed to spend about a week fixing it. Right now, we are saving one to two weeks. Though, it depends on the complexity of the pipeline, we are definitely seeing a lot of time being saved."
"The most valuable features are the option of integration with a variety of protocols, languages, and origins."
"The scheduling within the data engineering pipeline is very much appreciated, and it has a wide range of connectors for connecting to any data sources like SQL Server, AWS, Azure, etc. We have used it with Kafka, Hadoop, and Azure Data Factory Datasets. Connecting to these systems with StreamSets is very easy."
"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."
"It is really easy to set up and the interface is easy to use."
"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 customize it to do what you need. Many other tools have started to use features similar to those introduced by StreamSets, like automated workflows that are easy to set up."
"I like the data vault implementations."
"This is a fantastically robust DW tool that will make you at least 10 times faster in producing a DW."
"Quickly develops a data warehouse for our organization with documentation and can track back/forward features."
"Support is absolutely excellent, efficient, and timely."
"RED generates comprehensive documentation and regenerates it as quickly as things changes, but it also provides impact documentation."
"WhereScape RED has improved our business's ability to generate needed reporting without requiring a large team of developers to manually code all of the necessary plumbing."
"RED has provided us the ability to integrate, stage, and transform data from diverse sources into an enterprise-grade data warehouse which meets the needs of my organization, but it also enables us to easily and quickly make ETL or DW changes."
"The most valuable feature is the metadata generated code."
 

Cons

"The monitoring visualization is not that user-friendly. It should include other features to visualize things, like how many records were streamed from a source to a destination on a particular date."
"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."
"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."
"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."
"One thing that I would like to add is the ability to manually enter data. The way the solution currently works is we don't have the option to manually change the data at any point in time. Being able to do that will allow us to do everything that we want to do with our data. Sometimes, we need to manually manipulate the data to make it more accurate in case our prior bifurcation filters are not good. If we have the option to manually enter the data or make the exact iterations on the data set, that would be a good thing."
"One area for improvement could be the cloud storage server speed, as we have faced some latency issues here and there."
"If you use JDBC Lookup, for example, it generally takes a long time to process data."
"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."
"Project-based searching of data objects in the data warehouse browser needs to be improved."
"The ability to execute SSIS projects within WhereScape would be nice because we have a lot of packages that are too cumbersome to recreate."
"The scheduled jobs which are run by the WhereScape scheduler seem to be a strangely separate animal. Unlike all other WhereScape objects, jobs cannot be added to WhereScape projects. Also, unlike all other objects, jobs also cannot be deleted using a WhereScape deployment application."
"Jobs cannot be deleted via the deployment package. When deploying from dev to QA or production, a job has to be retired. The job has to be manually removed from the target environment."
"Improve the object renaming ability (it works, but it could be more automated)."
"Technical support isn't the best."
"They need a more robust support center. It has been a bit difficult to find solutions to problems that are out-of-the-box."
"Customization could be better."
 

Pricing and Cost Advice

"We use the free version. It's great for a public, free release. Our stance is that the paid support model is too expensive to get into. They should honestly reevaluate that."
"I believe the pricing is not equitable."
"Its pricing is pretty much up to the mark. For smaller enterprises, it could be a big price to pay at the initial stage of operations, but the moment you have the Seed B or Seed C funding and you want to scale up your operations and aren't much worried about the funds, at that point in time, you would need a solution that could be scaled."
"We are running the community version right now, which can be used free of charge."
"It's not expensive because you pay per month, and the tasks you can perform with it are huge. It's reliable and cost-effective."
"StreamSets is an expensive solution."
"StreamSets is expensive, especially for small businesses."
"The pricing is affordable for any business."
"Factor in the price of specialized consulting who know this product. They're hard to find and expensive."
"Speed to market of a warehouse solution at a relatively inexpensive price point."
"Our company purchased a corporate unlimited license."
"ROI is at least 10 times."
report
Use our free recommendation engine to learn which Data Integration solutions are best for your needs.
824,067 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
Computer Software Company
10%
Manufacturing Company
10%
Insurance Company
7%
Financial Services Firm
19%
Insurance Company
9%
Government
9%
Manufacturing Company
8%
 

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?
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 ...
What is your primary use case for StreamSets?
StreamSets is used for data transformation rather than ETL processes. It focuses on transforming data directly from sources without handling the extraction part of the process. The transformed data...
Ask a question
Earn 20 points
 

Comparisons

 

Learn More

Video not available
Video not available
 

Overview

 

Sample Customers

Availity, BT Group, Humana, Deluxe, GSK, RingCentral, IBM, Shell, SamTrans, State of Ohio, TalentFulfilled, TechBridge
British American Tobacco, Cornell University, Allianz Benelux, Finnair, Solarwinds and many more.
Find out what your peers are saying about StreamSets vs. WhereScape RED and other solutions. Updated: November 2024.
824,067 professionals have used our research since 2012.