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

Qlik Replicate vs StreamSets comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 19, 2024

Review summaries and opinions

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

Categories and Ranking

Qlik Replicate
Ranking in Data Integration
14th
Average Rating
8.2
Reviews Sentiment
6.9
Number of Reviews
16
Ranking in other categories
No ranking in other categories
StreamSets
Ranking in Data Integration
9th
Average Rating
8.4
Reviews Sentiment
7.1
Number of Reviews
21
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of January 2025, in the Data Integration category, the mindshare of Qlik Replicate is 3.6%, up from 3.1% compared to the previous year. The mindshare of StreamSets is 1.9%, up from 1.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Data Integration
 

Featured Reviews

KrishnaBaddam - PeerSpot reviewer
Lightweight tool, ensures that data is replicated across different systems and simplify complex tasks such as defining relationships
Qlik Compose is something that will automate user's overall data modernization. Here data modernization includes data modeling, ETL jobs, etc. But the advantage is users can automate the overall process of data engineering and data modeling through Qlik Compose. I think that's useful when users are able to manage 60% of the workload automated. That will be very useful. That's fantastic. Replicate does not have a great AI capability. AI capabilities are present in Qlik Sense. Qlik Replicate is a very light tool. It is only meant to capture data from the log files, get the data, and transfer it, read that table structure, create the table structure, and transfer the data whenever there is a change. So, it basically integrates with the kernel of the operating system. The way it works is that these replicate tools will integrate with the kernel of the operating system, and they will access the redo log files of the database. The redo log should have access to all the files of the structure of the schema, too. So, using that technique, they redo all the data structures, create a similar structure, and replicate the structure in the target schema, table, and database. After that is done, it will start tracing the instances that are happening. For example, if data is inserted into the table, then an insert is fired on the statement on the table. So, that particular insert is captured. And based on that insert statement, it will pull the SQL query and say, "Okay, there is an insert. I need to get that data." It will get the data from the redo log itself rather than going to a database. Then, it will just pass that transaction into the target system, where it will just insert the data. And this happens instantaneously, within a microsecond. So, if there is an insert, an update, or a delete, everything is transferred immediately. It is picked from the redo log because it comes to the redo log, and then the redo log sends it to Qlik Replicate and Replicate to the target system on which Replicate is installed.
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.

Quotes from Members

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

Pros

"Qlik Replicate's ability to correctly map and replicate data, especially when converting complex fields like packed decimal fields into integers, stands out."
"Qlik Replicate stands out with its cutting-edge technology and its ability to handle diverse data management tasks. This powerful tool allows us to efficiently and swiftly load data into various data stores or destinations, while also enabling easy distribution across different endpoints. A notable feature is its capability to reload data from multiple sources by creating multiple tasks within a brief timeframe of fifteen to twenty minutes. This eliminates the need for manual intervention and ensures quick data loading from different tables."
"A valuable feature of Qlik Replicate is that you do not need ETL. It's easy to use—you choose two systems and it automatically replicates them. Even if there is no CDC available, if you insert it and update it, and there is nothing to find out, then you can use Qlik Replicate. It's a good product."
"It's very user-friendly when it comes to settings and configuration. It also offers very detailed logging about warnings and errors."
"Low-priced reporting and analytics solution, with good scalability and stability. It has on-premises and cloud versions that are cohesive and can integrate well."
"Support has been great."
"Great with replicating and updating records."
"It enables us to transform data at the latest stage rather than in ETL loads, so it's more ELT which is one of the advantages. It is also in near real-time, which brings significant advantage for our embedded analytics approach."
"The best feature that I really like is the integration."
"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 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."
"In StreamSets, everything is in one place."
"StreamSets Transformer is a good feature because it helps you when you are developing applications and when you don't want to write a lot of code. That is the best feature overall."
"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."
"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."
"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."
 

Cons

"Support for this product is not great. It needs to be improved."
"We would like to see more details in messages about errors with the system."
"Some features on the graphical user interface are clunky."
"This product could be improved by providing more insight regarding errors. One of our customers that uses Qlik Replicate has had an issue. We tried to debug it, but we could not trace the error message. The infrastructure site should give us more insight about errors. Qlik Replicate is not a business solution, it's an IT solution. The reporting tools and bug site should be improved."
"In various scenarios, an important consideration is when we encounter issues and Qlik Replicate suggests reloading a specific table. If we face any problems or encounter errors with that table, it becomes necessary to make a change in Qlik Replicate. Performing a full reload every time is not feasible or practical. Instead, we should identify the specific issues and address them without repeating the entire reloading process. Based on this approach, we can investigate and resolve the problem by performing targeted loads from the source itself. This change aligns with my perspective and is something I would like to implement."
"The product should improve its licensing limitation."
"In the next release, I would like to see closer integration with data catalyst."
"It's not possible to replicate the QVC files in data analytics."
"If you use JDBC Lookup, for example, it generally takes a long time to process data."
"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."
"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."
"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."
"Visualization and monitoring need to be improved and refined."
"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."
"StreamSet works great for batch processing but we are looking for something that is more real-time. We need latency in numbers below milliseconds."
 

Pricing and Cost Advice

"Overall, Qlik is an expensive solution. You need to pay for all additional features that you would like to use."
"Qlik Replicate is mainly suited for large companies. However, it is too costly for small businesses. Its pricing is high."
"Pricing for this solution is very reasonable."
"Qlik Replicate is not expensive, compared to GoldenGate."
"On a scale from one to ten, where one is cheap, and ten is expensive, I rate Qlik Replicate's pricing a nine out of ten."
"Unlike Azure, where you pay based on consumption, Qlik Replicate seems to charge per endpoint."
"I believe the pricing is not equitable."
"StreamSets is an expensive solution."
"There are two editions, Professional and Enterprise, and there is a free trial. We're using the Professional edition and it is competitively priced."
"There are different versions of the product. One is the corporate license version, and the other one is the open-source or free version. I have been using the corporate license version, but they have recently launched a new open-source version so that anybody can create an account and use it. The licensing cost varies from customer to customer. I don't have a lot of input on that. It is taken care of by PMO, and they seem fine with its pricing model. It is being used enterprise-wide. They seem to have got a good deal for StreamSets."
"It's not so favorable for small companies."
"The pricing is affordable for any business."
"It has a CPU core-based licensing, which works for us and is quite good."
"The overall cost is very flexible so it is not a burden for our organization... However, the cost should be improved. For small and mid-size organizations it might be a challenge."
report
Use our free recommendation engine to learn which Data Integration solutions are best for your needs.
830,526 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Computer Software Company
12%
Manufacturing Company
10%
Insurance Company
9%
Financial Services Firm
18%
Computer Software Company
11%
Manufacturing Company
10%
Insurance Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Qlik Replicate?
The main valuable feature is its real-time change data capture (CDC) capabilities, which process data with minimal latency. There is not much delay. It also performs well with batch-wise data appli...
What needs improvement with Qlik Replicate?
Some features on the graphical user interface are clunky. Accessing certain functions like replicating from a table after a specific date requires obscure key combinations, which could be made more...
What is your primary use case for Qlik Replicate?
The primary use case is using Qlik Replicate to interface with DB2, allowing for efficient data replication from various sources into a common one or other destinations. It is particularly benefici...
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...
 

Also Known As

Replicate, Qlik Replicate
No data available
 

Learn More

Video not available
 

Overview

 

Sample Customers

American Cancer Society, Fanzz, SM Retail, Smart Modular, Tangerine Bank, Wellcare
Availity, BT Group, Humana, Deluxe, GSK, RingCentral, IBM, Shell, SamTrans, State of Ohio, TalentFulfilled, TechBridge
Find out what your peers are saying about Qlik Replicate vs. StreamSets and other solutions. Updated: January 2025.
830,526 professionals have used our research since 2012.